VMware

Primcoat builds your hardened image, uploads it to VMware vSphere, and registers it as a Content Library item. Primcoat installs VMware Tools during the build, so the guest has a clean shutdown path, time synchronization, and usable metrics rather than being a black box to the host.

What you configure

A publish target holds the vCenter endpoint and credentials, and the Content Library to publish into. You define the image name, and add version information and other details as you like.

VMware on AWS, Azure, and Google Cloud

Managed VMware clouds are full vSphere environments, so Primcoat publishes into them exactly as it does on-premises — point the target at the environment’s vCenter and Content Library. This covers VMware Cloud on AWS, Azure VMware Solution, and Google Cloud VMware Engine: the same hardened image, the same Content Library item, whether your vCenter runs in your datacenter or on a hyperscaler.