[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eAlloyDB for PostgreSQL is a fully managed database service where Google handles infrastructure, security, and maintenance, including hardware, encryption, and scheduled updates.\u003c/p\u003e\n"],["\u003cp\u003eAs an AlloyDB customer, you are responsible for the configuration, operation, and optimization of your database instances to meet your specific workload requirements.\u003c/p\u003e\n"],["\u003cp\u003eGoogle provides monitoring tools and features like backups, disaster recovery, and high availability to enhance the reliability and performance of AlloyDB instances.\u003c/p\u003e\n"],["\u003cp\u003eCustomers need to create and manage databases, secure access, configure connectivity, and manage performance and storage quota based on their needs.\u003c/p\u003e\n"]]],[],null,["# AlloyDB for PostgreSQL shared responsibility\n\nThis page describes what you, as an AlloyDB for PostgreSQL customer, are responsible\nfor, and what Google is responsible for.\n\nAlloyDB is a fully managed database service that simplifies\ndeployment, maintenance, and management of relational databases in the Google Cloud.\nAlloyDB offers meaningful insights and manageability features,\nsignificantly reducing user toil.\n\nAs an AlloyDB customer, you are responsible for configuring and\noperating AlloyDB to ensure that your workloads get the most\nvalue from the service.\n\nGoogle's responsibilities\n-------------------------\n\n- Provision and maintain the underlying infrastructure, including hardware, firmware, kernel, OS, storage, network and more:\n - [Secure](/docs/security/infrastructure/design#secure_low_level_infrastructure) the low-level infrastructure, which includes the physical premises, the hardware in Google data centers, and the low-level software stack running on the machines.\n - Encrypt data in an AlloyDB instance [at rest](/docs/security/encryption/default-encryption) by default and enable customer-managed encryption [in transit](/docs/security/encryption-in-transit).\n- Schedule [maintenance](/alloydb/docs/maintenance#timing) window to apply the latest AlloyDB version:\n - Provide maintenance notifications.\n - Allow maintenance window configuration.\n- Provide configuration and tools to secure your AlloyDB instances:\n - Provide limited access to database-specific features available to customers using flags, stored procedures, and plugins.\n - Increase self-service [cluster storage quota](/alloydb/docs/recommender-increase-cluster-storage-quota). If you need to store more than 16TiB of data in a cluster.\n- Provide monitoring telemetry for various instance components including but not limited to:\n - CPU\n - Storage\n - Network\n - Memory\n - User connections\n- Let you configure continuous backups that allows point-in-time (PITR) the cluster to restore to any point within your retention.\n- Provide [disaster recovery](/alloydb/docs/cross-region-replication/about-cross-region-replication) capabilities in case of regional outages for instances configured with cross-region read replicas and instances configured with multi-region backups.\n- Provide high availability in case of zonal outages on instances configured for [high availability (HA)](/alloydb/docs/instance-primary-secondary-failover).\n- Provide workload introspection capabilities and insights with [Query insights](/alloydb/docs/query-insights-overview).\n- Provide Google Cloud integrations for [Identity and Access Management (IAM)](/alloydb/docs/manage-iam-authn), [tags](/alloydb/docs/manage-tags), [Cloud Key Management Service](/alloydb/docs/cmek) and [Network Intelligence Center](/network-intelligence-center/docs).\n\nCustomer responsibilities\n-------------------------\n\n- [Create](/alloydb/docs/cluster-create) clusters and instances with appropriate major version, location, size, and [database flags](/alloydb/docs/reference/database-flags).\n- Create and administer databases and any user-created code on the instance.\n- [Secure](/alloydb/docs/user-grant-access) access, authentication, and authorization using appropriate controls.\n- Configure and troubleshoot connectivity from client-side tooling to the AlloyDB instance.\n- Configure the AlloyDB instance for [high availability](/alloydb/docs/instance-primary-secondary-failover) and zonal or regional [disaster recovery](/alloydb/docs/cross-region-replication/about-cross-region-replication).\n- Use the [maintenance features](/alloydb/docs/maintenance#timing) to minimize the business impact from maintenance events, and to allow for timely application of critical security updates and necessary version upgrades.\n- Manage, tune, and optimize the database performance based on the workload and instance configuration.\n- Make sure you have [storage quota](/alloydb/docs/recommender-increase-cluster-storage-quota) approval to accommodate future growth necessary for critical database maintenance events."]]
