AWS AmazonRDS documentation change
Summary
Removed step about filtering for Babelfish-supported versions and renumbered subsequent steps in the Babelfish creation workflow
Security assessment
This change is purely procedural and organizational - it removes a filtering step and renumbers the remaining steps in the Babelfish database creation process. There is no evidence of addressing security vulnerabilities, patching issues, or adding security features. The change maintains existing security-related steps (like master password, encryption, deletion protection) but doesn't modify their content or add new security documentation.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/babelfish-create.md b/AmazonRDS/latest/AuroraUserGuide/babelfish-create.md index 1401089d7..8a39515e2 100644 --- a//AmazonRDS/latest/AuroraUserGuide/babelfish-create.md +++ b//AmazonRDS/latest/AuroraUserGuide/babelfish-create.md @@ -29,3 +29 @@ In an Aurora PostgreSQL cluster, the `babelfish_db` database name is reserved fo - 4. Choose **Show filters** , and then choose **Show versions that support the Babelfish for PostgreSQL feature** to list the engine types that support Babelfish. Babelfish is currently supported on Aurora PostgreSQL 13.4 and higher versions. - - 5. For **Available versions** , choose an Aurora PostgreSQL version. To get the latest Babelfish features, choose the highest Aurora PostgreSQL major version. + 4. For **Available versions** , choose an Aurora PostgreSQL version. To get the latest Babelfish features, choose the highest Aurora PostgreSQL major version. Babelfish is supported on Aurora PostgreSQL 13.4 and higher versions. @@ -35 +33 @@ In an Aurora PostgreSQL cluster, the `babelfish_db` database name is reserved fo - 6. For **Templates** , choose the template that matches your use case. + 5. For **Templates** , choose the template that matches your use case. @@ -37 +35 @@ In an Aurora PostgreSQL cluster, the `babelfish_db` database name is reserved fo - 7. For **DB cluster identifier** , enter a name that you can easily find later in the DB cluster list. + 6. For **DB cluster identifier** , enter a name that you can easily find later in the DB cluster list. @@ -39 +37 @@ In an Aurora PostgreSQL cluster, the `babelfish_db` database name is reserved fo - 8. For **Master username** , enter an administrator user name. The default value for Aurora PostgreSQL is `postgres`. You can accept the default or choose a different name. For example, to follow the naming convention used on your SQL Server databases, you can enter `sa` (system administrator) for the Master username. + 7. For **Master username** , enter an administrator user name. The default value for Aurora PostgreSQL is `postgres`. You can accept the default or choose a different name. For example, to follow the naming convention used on your SQL Server databases, you can enter `sa` (system administrator) for the Master username. @@ -47 +45 @@ Master username must always use lowercase characters failing which the DB cluste - 9. For **Master password** , create a strong password and confirm the password. + 8. For **Master password** , create a strong password and confirm the password. @@ -49 +47 @@ Master username must always use lowercase characters failing which the DB cluste - 10. For the options that follow, until the **Babelfish settings** section, specify your DB cluster settings. For information about each setting, see [Settings for Aurora DB clusters](./Aurora.CreateInstance.html#Aurora.CreateInstance.Settings). + 9. For the options that follow, until the **Babelfish settings** section, specify your DB cluster settings. For information about each setting, see [Settings for Aurora DB clusters](./Aurora.CreateInstance.html#Aurora.CreateInstance.Settings). @@ -51 +49 @@ Master username must always use lowercase characters failing which the DB cluste - 11. To make Babelfish functionality available, select the **Turn on Babelfish** box. + 10. To make Babelfish functionality available, select the **Turn on Babelfish** box. @@ -55 +53 @@ Master username must always use lowercase characters failing which the DB cluste - 12. For **DB cluster parameter group** , do one of the following: + 11. For **DB cluster parameter group** , do one of the following: @@ -63 +61 @@ If you use an existing group, provide the group name in the box that follows. - 13. For **Database migration mode** , choose one of the following: + 12. For **Database migration mode** , choose one of the following: @@ -77 +75 @@ From Aurora PostgreSQL 16 version, **Multiple databases** is chosen by default a - 14. For **Default collation locale** , enter your server locale. The default is `en-US`. For detailed information about collations, see [Understanding Collations in Babelfish for Aurora PostgreSQL](./babelfish-collations.html). + 13. For **Default collation locale** , enter your server locale. The default is `en-US`. For detailed information about collations, see [Understanding Collations in Babelfish for Aurora PostgreSQL](./babelfish-collations.html). @@ -79 +77 @@ From Aurora PostgreSQL 16 version, **Multiple databases** is chosen by default a - 15. For **Collation name** field, enter your default collation. The default is `sql_latin1_general_cp1_ci_as`. For detailed information, see [Understanding Collations in Babelfish for Aurora PostgreSQL](./babelfish-collations.html). + 14. For **Collation name** field, enter your default collation. The default is `sql_latin1_general_cp1_ci_as`. For detailed information, see [Understanding Collations in Babelfish for Aurora PostgreSQL](./babelfish-collations.html). @@ -81 +79 @@ From Aurora PostgreSQL 16 version, **Multiple databases** is chosen by default a - 16. For **Babelfish TDS port** , enter the default port `1433`. Currently, Babelfish only supports port `1433` for your DB cluster. + 15. For **Babelfish TDS port** , enter the default port `1433`. Currently, Babelfish only supports port `1433` for your DB cluster. @@ -83 +81 @@ From Aurora PostgreSQL 16 version, **Multiple databases** is chosen by default a - 17. For **DB parameter group** , choose a parameter group or have Aurora create a new group for you with default settings. + 16. For **DB parameter group** , choose a parameter group or have Aurora create a new group for you with default settings. @@ -85 +83 @@ From Aurora PostgreSQL 16 version, **Multiple databases** is chosen by default a - 18. For **Failover priority** , choose a failover priority for the instance. If you don't choose a value, the default is `tier-1`. This priority determines the order in which replicas are promoted when recovering from a primary instance failure. For more information, see [Fault tolerance for an Aurora DB cluster](./Concepts.AuroraHighAvailability.html#Aurora.Managing.FaultTolerance). + 17. For **Failover priority** , choose a failover priority for the instance. If you don't choose a value, the default is `tier-1`. This priority determines the order in which replicas are promoted when recovering from a primary instance failure. For more information, see [Fault tolerance for an Aurora DB cluster](./Concepts.AuroraHighAvailability.html#Aurora.Managing.FaultTolerance). @@ -87 +85 @@ From Aurora PostgreSQL 16 version, **Multiple databases** is chosen by default a - 19. For **Backup retention period** , choose the length of time (1–35 days) that Aurora retains backup copies of the database. You can use backup copies for point-in-time restores (PITR) of your database down to the second. The default retention period is seven days. + 18. For **Backup retention period** , choose the length of time (1–35 days) that Aurora retains backup copies of the database. You can use backup copies for point-in-time restores (PITR) of your database down to the second. The default retention period is seven days. @@ -91 +89 @@ From Aurora PostgreSQL 16 version, **Multiple databases** is chosen by default a - 20. Choose **Copy tags to snapshots** to copy any DB instance tags to a DB snapshot when you create a snapshot. + 19. Choose **Copy tags to snapshots** to copy any DB instance tags to a DB snapshot when you create a snapshot. @@ -97 +95 @@ When restoring a DB cluster from a snapshot, it does not restore as a Babelfish - 21. Choose **Enable encryption** to turn on encryption at rest (Aurora storage encryption) for this DB cluster. + 20. Choose **Enable encryption** to turn on encryption at rest (Aurora storage encryption) for this DB cluster. @@ -99 +97 @@ When restoring a DB cluster from a snapshot, it does not restore as a Babelfish - 22. Choose **Enable Performance Insights** to turn on Amazon RDS Performance Insights. + 21. Choose **Enable Performance Insights** to turn on Amazon RDS Performance Insights. @@ -101 +99 @@ When restoring a DB cluster from a snapshot, it does not restore as a Babelfish - 23. Choose **Enable Enhanced monitoring** to start gathering metrics in real time for the operating system that your DB cluster runs on. + 22. Choose **Enable Enhanced monitoring** to start gathering metrics in real time for the operating system that your DB cluster runs on. @@ -103 +101 @@ When restoring a DB cluster from a snapshot, it does not restore as a Babelfish - 24. Choose **PostgreSQL log** to publish the log files to Amazon CloudWatch Logs. + 23. Choose **PostgreSQL log** to publish the log files to Amazon CloudWatch Logs. @@ -105 +103 @@ When restoring a DB cluster from a snapshot, it does not restore as a Babelfish - 25. Choose **Enable auto minor version upgrade** to automatically update your Aurora DB cluster when a minor version upgrade is available. + 24. Choose **Enable auto minor version upgrade** to automatically update your Aurora DB cluster when a minor version upgrade is available. @@ -107 +105 @@ When restoring a DB cluster from a snapshot, it does not restore as a Babelfish - 26. For **Maintenance window** , do the following: + 25. For **Maintenance window** , do the following: @@ -113 +111 @@ When restoring a DB cluster from a snapshot, it does not restore as a Babelfish - 27. Select the **Enable deletion protection** box to protect your database from being deleted by accident. + 26. Select the **Enable deletion protection** box to protect your database from being deleted by accident. @@ -119 +117 @@ If you turn on this feature, you can't directly delete the database. Instead, yo - 28. Choose **Create database**. + 27. Choose **Create database**.