From e0b9b938d8b711a9b2229bc5d096908827bf9549 Mon Sep 17 00:00:00 2001 From: Paul Cornell Date: Wed, 15 Jan 2025 09:56:53 -0800 Subject: [PATCH 1/2] PostgreSQL connectors: enable or restrict public access to Amazon RDS for PostgreSQL instances --- snippets/general-shared-text/postgresql.mdx | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/snippets/general-shared-text/postgresql.mdx b/snippets/general-shared-text/postgresql.mdx index 6df037ca..70e346ea 100644 --- a/snippets/general-shared-text/postgresql.mdx +++ b/snippets/general-shared-text/postgresql.mdx @@ -48,6 +48,20 @@ import AllowIPAddressRanges from '/snippets/general-shared-text/ip-address-range [Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.RDSSecurityGroups.html) or [Azure Database for PostgreSQL](https://learn.microsoft.com/azure/postgresql/flexible-server/how-to-manage-firewall-portal#create-a-firewall-rule-after-server-is-created). + + For Amazon RDS for PostgreSQL, Amazon recommends that you do set the instance's **Public access** setting to **No** by default, as this + approach is more secure. This means that no + resources can connect to the instance outside of the instance's associated Virtual Private Cloud (VPC) without extra configuration. + [Learn more](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Hiding). + [Access an Amazon RDS instance in a VPC](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.Scenarios.html). + + If you must enable public access, set the instance's **Public access** setting to **Yes**, and then adjust the instance's related + security group to allow this access. + [Learn how](https://repost.aws/en/questions/QUxemKa9u5TV6CmLiO-r5prg/lost-public-access-to-aws-rds-postgresql-instance). + + [Troubleshoot issues with connecting to Amazon RDS instances](https://repost.aws/knowledge-center/rds-connectivity-instance-subnet-vpc). + + - A database in the instance. - For Amazon RDS for PostgreSQL and Azure Database for PostgreSQL, the default database name is `postgres` unless a custom database name was specified during the instance creation process. From 7d185b7c6ce88251671a3079c37c1dad117286c8 Mon Sep 17 00:00:00 2001 From: Paul Cornell Date: Wed, 15 Jan 2025 09:59:39 -0800 Subject: [PATCH 2/2] Fix grammar: remove 'do' --- snippets/general-shared-text/postgresql.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/snippets/general-shared-text/postgresql.mdx b/snippets/general-shared-text/postgresql.mdx index 70e346ea..85d6a18e 100644 --- a/snippets/general-shared-text/postgresql.mdx +++ b/snippets/general-shared-text/postgresql.mdx @@ -49,7 +49,7 @@ import AllowIPAddressRanges from '/snippets/general-shared-text/ip-address-range [Azure Database for PostgreSQL](https://learn.microsoft.com/azure/postgresql/flexible-server/how-to-manage-firewall-portal#create-a-firewall-rule-after-server-is-created). - For Amazon RDS for PostgreSQL, Amazon recommends that you do set the instance's **Public access** setting to **No** by default, as this + For Amazon RDS for PostgreSQL, Amazon recommends that you set the instance's **Public access** setting to **No** by default, as this approach is more secure. This means that no resources can connect to the instance outside of the instance's associated Virtual Private Cloud (VPC) without extra configuration. [Learn more](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html#USER_VPC.Hiding).