AWS AmazonRDS documentation change
Summary
Complete restructuring of the Aurora PostgreSQL getting started guide - removed detailed step-by-step tutorial and replaced with a brief introduction and links to separate 'full configuration' and 'express configuration' pages.
Security assessment
This is a documentation reorganization that removes detailed implementation steps but doesn't address any specific security vulnerability. The change removes security-related content like warnings about SSH access (0.0.0.0/0), security best practices for production environments, and SSL/TLS connection guidance, but this appears to be part of moving that content to separate pages rather than addressing a security incident.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.CreatingConnecting.AuroraPostgreSQL.md b/AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.CreatingConnecting.AuroraPostgreSQL.md index a9465e8c7..080de5aba 100644 --- a//AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.CreatingConnecting.AuroraPostgreSQL.md +++ b//AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.CreatingConnecting.AuroraPostgreSQL.md @@ -5,2 +4,0 @@ -PrerequisitesStep 1: Create an EC2 instanceStep 2: Create an Aurora PostgreSQL DB cluster(Optional) Create VPC, EC2 instance, and Aurora PostgreSQL cluster using CloudFormationStep 3: Connect to an Aurora PostgreSQL DB clusterStep 4: Delete the EC2 instance and DB cluster(Optional) Delete the EC2 instance and DB cluster created with CloudFormation(Optional) Connect your DB cluster to a Lambda function - @@ -9,24 +7 @@ PrerequisitesStep 1: Create an EC2 instanceStep 2: Create an Aurora PostgreSQL D -This tutorial creates an EC2 instance and an Aurora PostgreSQL DB cluster. The tutorial shows you how to access the DB cluster from the EC2 instance using a standard PostgreSQL client. As a best practice, this tutorial creates a private DB cluster in a virtual private cloud (VPC). In most cases, other resources in the same VPC, such as EC2 instances, can access the DB cluster, but resources outside of the VPC can't access it. - -After you complete the tutorial, there is a public and private subnet in each Availability Zone in your VPC. In one Availability Zone, the EC2 instance is in the public subnet, and the DB instance is in the private subnet. - -###### Important - -There's no charge for creating an AWS account. However, by completing this tutorial, you might incur costs for the AWS resources that you use. You can delete these resources after you complete the tutorial if they are no longer needed. - -The following diagram shows the configuration when the tutorial is complete. - - - -This tutorial allows you to create your resources by using one of the following methods: - - 1. Use the AWS Management Console ‐ Step 1: Create an EC2 instanceand Step 2: Create an Aurora PostgreSQL DB cluster - - 2. Use CloudFormation to create the database instance and EC2 instance ‐ (Optional) Create VPC, EC2 instance, and Aurora PostgreSQL cluster using CloudFormation - - - - -The first method uses **Easy create** to create a private Aurora PostgreSQL DB cluster with the AWS Management Console. Here, you specify only the DB engine type, DB instance size, and DB cluster identifier. **Easy create** uses the default settings for the other configuration options. - -When you use **Standard create** instead, you can specify more configuration options when you create a DB cluster. These options include settings for availability, security, backups, and maintenance. To create a public DB cluster, you must use **Standard create**. For information, see [Creating an Amazon Aurora DB cluster](./Aurora.CreateInstance.html). +There are two ways of creating an Aurora PostgreSQL cluster: full configuration and express configuration. Please refer to the sections below to understand more about these 2 types of creates. @@ -36,366 +11 @@ When you use **Standard create** instead, you can specify more configuration opt - * Prerequisites - - * Step 1: Create an EC2 instance - - * Step 2: Create an Aurora PostgreSQL DB cluster - - * (Optional) Create VPC, EC2 instance, and Aurora PostgreSQL cluster using CloudFormation - - * Step 3: Connect to an Aurora PostgreSQL DB cluster - - * Step 4: Delete the EC2 instance and DB cluster - - * (Optional) Delete the EC2 instance and DB cluster created with CloudFormation - - * (Optional) Connect your DB cluster to a Lambda function - - - - -## Prerequisites - -Before you begin, complete the steps in the following sections: - - * [Sign up for an AWS account](./CHAP_SettingUp_Aurora.html#sign-up-for-aws) - - * [Create a user with administrative access](./CHAP_SettingUp_Aurora.html#create-an-admin) - - - - -## Step 1: Create an EC2 instance - -Create an Amazon EC2 instance that you will use to connect to your database. - -###### To create an EC2 instance - - 1. Sign in to the AWS Management Console and open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). - - 2. In the upper-right corner of the AWS Management Console, choose the AWS Region in which you want to create the EC2 instance. - - 3. Choose **EC2 Dashboard** , and then choose **Launch instance** , as shown in the following image. - - - -The **Launch an instance** page opens. - - 4. Choose the following settings on the **Launch an instance** page. - - 1. Under **Name and tags** , for **Name** , enter `ec2-database-connect`. - - 2. Under **Application and OS Images (Amazon Machine Image)** , choose **Amazon Linux** , and then choose the **Amazon Linux 2023 AMI**. Keep the default selections for the other choices. - - - - 3. Under **Instance type** , choose **t2.micro**. - - 4. Under **Key pair (login)** , choose a **Key pair name** to use an existing key pair. To create a new key pair for the Amazon EC2 instance, choose **Create new key pair** and then use the **Create key pair** window to create it. - -For more information about creating a new key pair, see [Create a key pair](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/get-set-up-for-amazon-ec2.html#create-a-key-pair) in the _Amazon EC2 User Guide_. - - 5. For **Allow SSH traffic** in **Network settings** , choose the source of SSH connections to the EC2 instance. - -You can choose **My IP** if the displayed IP address is correct for SSH connections. Otherwise, you can determine the IP address to use to connect to EC2 instances in your VPC using Secure Shell (SSH). To determine your public IP address, in a different browser window or tab, you can use the service at [https://checkip.amazonaws.com](https://checkip.amazonaws.com/). An example of an IP address is 192.0.2.1/32. - -In many cases, you might connect through an internet service provider (ISP) or from behind your firewall without a static IP address. If so, make sure to determine the range of IP addresses used by client computers. - -###### Warning - -If you use `0.0.0.0/0` for SSH access, you make it possible for all IP addresses to access your public EC2 instances using SSH. This approach is acceptable for a short time in a test environment, but it's unsafe for production environments. In production, authorize only a specific IP address or range of addresses to access your EC2 instances using SSH. - -The following image shows an example of the **Network settings** section. - - - - 6. Leave the default values for the remaining sections. - - 7. Review a summary of your EC2 instance configuration in the **Summary** panel, and when you're ready, choose **Launch instance**. - - 5. On the **Launch Status** page, note the identifier for your new EC2 instance, for example: `i-1234567890abcdef0`. - - - - 6. Choose the EC2 instance identifier to open the list of EC2 instances, and then select your EC2 instance. - - 7. In the **Details** tab, note the following values, which you need when you connect using SSH: - - 1. In **Instance summary** , note the value for **Public IPv4 DNS**. - - - - 2. In **Instance details** , note the value for **Key pair name**. - - - - 8. Wait until the **Instance state** for your EC2 instance has a status of **Running** before continuing. - - - - -## Step 2: Create an Aurora PostgreSQL DB cluster - -In this example, you use **Easy create** to create an Aurora PostgreSQL DB cluster with a db.t4g.large DB instance class. - -###### To create an Aurora PostgreSQL DB cluster with Easy create - - 1. Sign in to the AWS Management Console and open the Amazon RDS console at [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/). - - 2. In the upper-right corner of the Amazon RDS console, choose the AWS Region in which you want to create the DB cluster. - - 3. In the navigation pane, choose **Databases**. - - 4. Choose **Create database** , and make sure that **Easy create** is chosen. - - - - 5. In **Configuration** , choose **Aurora (PostgreSQL Compatible)** for **Engine type**. - - 6. For **DB instance size** , choose **Dev/Test**. - - 7. For **DB cluster identifier** , enter `database-test1`. - -The **Create database** page should look similar to the following image. - - - - 8. For **Master username** , enter a name for the user, or keep the default name (`postgres`). - - 9. To use an automatically generated master password for the DB cluster, select **Auto generate a password**. - -To enter your master password, make sure **Auto generate a password** is cleared, and then enter the same password in **Master password** and **Confirm password**. - - 10. To set up a connection with the EC2 instance you created previously, open **Set up EC2 connection -_optional_**. - -Select **Connect to an EC2 compute resource**. Choose the EC2 instance you created previously. - - - - 11. Open **View default settings for Easy create**. - - - -You can examine the default settings used with **Easy create**. The **Editable after database is created** column shows which options you can change after you create the database. - - * If a setting has **No** in that column, and you want a different setting, you can use **Standard create** to create the DB cluster. - - * If a setting has **Yes** in that column, and you want a different setting, you can either use **Standard create** to create the DB cluster, or modify the DB cluster after you create it to change the setting. - - 12. Choose **Create database**. - -To view the master username and password for the DB cluster, choose **View credential details**. - -You can use the username and password that appears to connect to the DB cluster as the master user. - -###### Important - -You can't view the master user password again. If you don't record it, you might have to change it. - -If you need to change the master user password after the DB cluster is available, you can modify the DB cluster to do so. For more information about modifying a DB cluster, see [Modifying an Amazon Aurora DB cluster](./Aurora.Modifying.html). - - 13. In the **Databases** list, choose the name of the new Aurora PostgreSQL DB cluster to show its details. - -The writer instance has a status of **Creating** until the DB cluster is ready to use. - - - -When the status of the writer instance changes to **Available** , you can connect to the DB cluster. Depending on the DB instance class and the amount of storage, it can take up to 20 minutes before the new DB cluster is available.