Google Cloud

Primcoat builds your hardened image, uploads it to Google Cloud Storage, and registers it as a custom image in your project. Primcoat adds the Google guest environment during the build — the guest agent and metadata-server integration Compute Engine relies on for SSH key propagation and instance metadata — so the image behaves like a native one rather than a stranger on the platform.

What you configure

A publish target holds the service account credentials, the destination project, the GCS staging bucket, and the image family to register into. You define the image name, and add version information and other details as you like.