View cluster and instance settings

This document describes settings for AlloyDB for PostgreSQL clusters and instances, which you can modify using the Google Cloud console or the gcloud CLI.

To view settings for a specific cluster or instance type, select one of the following.

Settings Modifiable after creation Values
Instance ID N Enter an instance ID to uniquely identify your instance.

Composed of lowercase and uppercase letters, numbers, and hyphens; must start with a letter. The total length must be a minimum length of 8 characters and a maximum of 128 characters.
Availability Y Select one of the following availability types:
  • Single zone (Zonal): This instance serves data from only one zone and is recommended for non-production setups. Any outages in that zone affects availability of your instance.
  • Multiple zones (Regional): This highly available instance supports automatic failover to another zone in the selected region and is recommended for production setups. The AlloyDB availability SLA of 99.99% (inclusive of maintenance) applies to a highly available instance.
Machine type Y Select from a list of supported machine-types such as n2-highmem-4, c4-highmem-4-lssd, or c4a-highmem-4-lssd. For more information, see Choose an AlloyDB machine type.
Private Service Connect: Allowed projects Y Required, if you created a Private Service Connect-enabled cluster.

Add a list of allowed projects when you create an AlloyDB instance by passing the list of projects with the --allowed-psc-projects flag.

Optional, if you want to enable outbound connectivity, then use the --psc-network-attachment-uri flag.
Network: Public IP Y Optional. Enable public IP to support inbound connections to your instance.
Public IP: Authorized external networks Y Optional. If Public IP is enabled, then provide a list of IP addresses authorized to connect through the internet to the instance. You can use CIDR notation to provide a list of IP addresses or IP ranges to authorize direct connections to the instance through a public IP. You don't need prior authorization for connections initiated through Auth Proxy or Language Connectors.
Network Security: Encryption options for connecting to an instance Y The Require SSL encryption is the default option and is enabled by default.

Optionally, you can select Enforce mTLS via AlloyDB connectors to force your instance to connect through AlloyDB AlloyDB Auth Proxy or AlloyDB Language Connectors. You can also select Allow unencrypted connections, but this action might expose sensitive data.
Database flags Y Add database flags to your instance from the list of supported flags.

Since AlloyDB auto scales storage, so you don't need to explicitly set a storage limit. Storage is automatically managed, and you're only charged for the storage that you use.