Skip to main content
Vendor service requirements and customer selections form an install service profile after field-ownership and supplied-version checks. The PostgreSQL catalog distinguishes a cloud service in the customer's account from a database managed by the appliance. Arrows show configuration, not database traffic.Vendor service requirements and customer selections form an install service profile after field-ownership and supplied-version checks. The PostgreSQL catalog distinguishes a cloud service in the customer's account from a database managed by the appliance. Arrows show configuration, not database traffic.Vendor service requirements and customer selections form an install service profile after field-ownership and supplied-version checks. The PostgreSQL catalog distinguishes a cloud service in the customer's account from a database managed by the appliance. Arrows show configuration, not database traffic.Vendor service requirements and customer selections form an install service profile after field-ownership and supplied-version checks. The PostgreSQL catalog distinguishes a cloud service in the customer's account from a database managed by the appliance. Arrows show configuration, not database traffic.
Your application’s form factor defines its PostgreSQL choices. You declare the service requirements and tuning; your customer selects an offered option and supplies its customer-owned configuration. The install profile combines those inputs after checking field ownership and any supplied version against applicable version constraints.

​
What the customer provides

Start with the PostgreSQL option offered by your application’s setup. The configuration depends on that option, rather than one connection form shared by every PostgreSQL deployment. See service configuration for how service choices fit into customer setup, and secrets for supplying secret references.

​
What changes in the deployment stack

A service adapter generates the database resources for the selected destination. For an application whose origin stack uses AWS RDS PostgreSQL or Aurora PostgreSQL, the supported mappings include:
  • CloudNativePG on Kubernetes. The deployment includes PostgreSQL cluster resources and the corresponding credential Secret. The database configuration is derived from the origin’s version, storage, replica, and resource settings.
  • Cloud SQL for PostgreSQL on Google Cloud. The deployment includes a Cloud SQL instance and, when the origin declares an application database, that database. The mapping carries supported engine, storage, availability, and backup settings into the destination configuration.
For example, selecting an offered CloudNativePG mapping produces a database on the install’s Kubernetes cluster. Selecting an offered Cloud SQL mapping produces a managed database in the customer’s Google Cloud environment. These choices have different operational ownership and configuration. Review the RDS PostgreSQL service adapter for the selected mapping’s behavior, including version, extension, networking, authentication, and backup differences. Check the application’s database requirements against that mapping before choosing it.

​
Other PostgreSQL integrations

PostgreSQL also appears in Kubernetes control-plane storage and Cloud Adapter backend storage. These uses have different configuration and ownership from an application’s relational database. See Private Kubernetes and Cloud Adapter for those separate areas.

​
What the customer takes on

Agree on operational ownership when choosing the database:

​
What stays your responsibility

You remain responsible for your application’s schema, migrations, query behavior, and data correctness. Confirm that the selected PostgreSQL version, extensions, and authentication model meet the application’s requirements. Plan any data transfer or migration as part of a database change. A service choice describes the destination configuration; moving an existing application’s data also requires an application-appropriate migration and validation procedure.

​
Authentication and rotation

Authentication is part of the selected database mapping. Use that mapping’s authentication procedure to plan database permissions, credential storage, and rotation. Keep application database logins separate from the cloud credentials used to deploy and manage the database. When setup requests a secret reference, use the designated secret store. Coordinate credential changes with the component that consumes the secret so it can establish new connections with the updated credential. See credentials and secrets for the customer’s credential responsibilities.

​
Where this fits

Customer-Provided Services describes the broader configuration area. Service adapters explains mappings between an origin service and a destination service. Use the service and integration selected for your install to determine the PostgreSQL configuration and ownership that apply.