Changelog

Self-service enhanced compliance BYOC clouds for Google Cloud (limited availability)

    New
    Google Cloud
    BYOC

Enhanced compliance clouds on Google Cloud are now in limited availability. Set them up yourself using bring your own cloud (BYOC) to run Aiven services in your own Google Cloud project under specific compliance requirements.

After you have a commitment deal with Aiven and Aiven enables the feature for your organization, create a custom cloud on Google Cloud and choose a deployment model:

  • hipaa for healthcare workloads that handle protected health information (PHI) under the Health Insurance Portability and Accountability Act (HIPAA)
  • pci_dss for payment workloads that require cardholder data environment (CDE) isolation under the Payment Card Industry Data Security Standard (PCI DSS)

These clouds keep your data in your Google Cloud project:

  • Services have no public internet access and are reachable only over VPC peering.
  • Outbound traffic, including traffic to Cloud Storage, is proxied through a bastion host.
  • Backups and cold data are stored in Google Cloud Storage buckets in your own project: one bucket for backups and one for cold data.
  • All resources are tagged with their compliance model for governance and audit traceability.
  • Services cannot be forked or migrated to another cloud.

For more information, see Enhanced compliance BYOC clouds.