AWS AmazonRDS: Updated AWS CLI parameter and fixed typos in Aurora PostgreSQL express config
Summary
Changed AWS CLI parameter from `--express-configuration` to `--with-express-configuration`, corrected capitalization of 'Aurora Standard', and fixed log export references.
Security assessment
The evidence shows a CLI parameter correction and minor typo fixes. No security vulnerabilities, features, or best practices are introduced or modified.
Evidence
-In two clicks, you can have an Aurora cluster with a serverless instance ready to use in seconds. You can also use the AWS Command Line Interface (AWS CLI) or [AWS SDKs](https://docs.aws.amazon.com/sdkref/latest/guide/overview.html) with the parameter `--express-configuration` to create both a cluster and an instance within the cluster with single API call which makes it ready for running queries in seconds. You have the flexibility to modify most of the settings during, and most other settings after the database creation. For more information about these settings, see Express configuration settings. Once created, you have access to most of the features and benefits of Aurora such as the ability to add readers for high availability and scalability, and automatic failover capabilities. Some options, such as specifying a customer managed encryption key, selecting specific engine versions, or associating the clusters with an Amazon Virtual Private Cloud (VPC), are only available when using the [Create with full configuration](./CHAP_GettingStartedAurora.AuroraPostgreSQL.FullConfig.html) option. This creation experience for Aurora PostgreSQL is also available with the [AWS Free Tier](https://aws.amazon.com/rds/free/).
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.md b/AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.md index c0fcba4be..85057700d 100644 --- a//AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.md +++ b//AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.AuroraPostgreSQL.ExpressConfig.md @@ -13 +13 @@ You can create and connect to an Aurora PostgreSQL serverless database in second -In two clicks, you can have an Aurora cluster with a serverless instance ready to use in seconds. You can also use the AWS Command Line Interface (AWS CLI) or [AWS SDKs](https://docs.aws.amazon.com/sdkref/latest/guide/overview.html) with the parameter `--express-configuration` to create both a cluster and an instance within the cluster with single API call which makes it ready for running queries in seconds. You have the flexibility to modify most of the settings during, and most other settings after the database creation. For more information about these settings, see Express configuration settings. Once created, you have access to most of the features and benefits of Aurora such as the ability to add readers for high availability and scalability, and automatic failover capabilities. Some options, such as specifying a customer managed encryption key, selecting specific engine versions, or associating the clusters with an Amazon Virtual Private Cloud (VPC), are only available when using the [Create with full configuration](./CHAP_GettingStartedAurora.AuroraPostgreSQL.FullConfig.html) option. This creation experience for Aurora PostgreSQL is also available with the [AWS Free Tier](https://aws.amazon.com/rds/free/). +In two clicks, you can have an Aurora cluster with a serverless instance ready to use in seconds. You can also use the AWS Command Line Interface (AWS CLI) or [AWS SDKs](https://docs.aws.amazon.com/sdkref/latest/guide/overview.html) with the parameter `--with-express-configuration` to create both a cluster and an instance within the cluster with single API call which makes it ready for running queries in seconds. You have the flexibility to modify most of the settings during, and most other settings after the database creation. For more information about these settings, see Express configuration settings. Once created, you have access to most of the features and benefits of Aurora such as the ability to add readers for high availability and scalability, and automatic failover capabilities. Some options, such as specifying a customer managed encryption key, selecting specific engine versions, or associating the clusters with an Amazon Virtual Private Cloud (VPC), are only available when using the [Create with full configuration](./CHAP_GettingStartedAurora.AuroraPostgreSQL.FullConfig.html) option. This creation experience for Aurora PostgreSQL is also available with the [AWS Free Tier](https://aws.amazon.com/rds/free/). @@ -131 +131 @@ Certificate authority | Clusters with express configuration are enabled with int -Cluster storage configuration | The storage type for the DB cluster: Aurora Standard or Aurora I/O-Optimized. For more information, see [Storage Configurations for Amazon Aurora DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Overview.StorageReliability.html). | Aurora standard by default. Can be changed after the create operation completes. +Cluster storage configuration | The storage type for the DB cluster: Aurora Standard or Aurora I/O-Optimized. For more information, see [Storage Configurations for Amazon Aurora DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Overview.StorageReliability.html). | Aurora Standard by default. Can be changed after the create operation completes. @@ -137 +137 @@ DB cluster parameter group | Clusters with express configuration use the Aurora -DB instance class | Clusters with express configuration start with an Aurora Serverless instance. | Aurora serverless instance. Can be changed after the create operation completes. +DB instance class | Clusters with express configuration start with an Aurora serverless instance. | Aurora serverless instance. Can be changed after the create operation completes. @@ -147 +147 @@ Initial database name | The name for your default database. If you don't provide -Log exports | In the Log exports section, choose the logs that you want to start publishing to Amazon CloudWatch Logs. For more information about publishing Aurora MySQL logs to CloudWatch Logs, see Publishing Amazon Aurora MySQL logs to Amazon CloudWatch Logs. For more information about publishing Aurora PostgreSQL logs to CloudWatch Logs, see Publishing Aurora PostgreSQL logs to Amazon CloudWatch Logs. | Disabled by default. Can be changed during or after the creation. +Log exports | In the Log exports section, choose the logs that you want to start publishing to Amazon CloudWatch Logs. For more information about publishing Aurora MySQL logs to CloudWatch Logs, see Publishing Aurora MySQL logs to Amazon CloudWatch Logs. For more information about publishing Aurora PostgreSQL logs to CloudWatch Logs, see Publishing Aurora PostgreSQL logs to Amazon CloudWatch Logs. | Disabled by default. Can be changed during or after the creation. @@ -347 +347 @@ If you disable the `rds_iam` role for the master username, you will lose access - * Clusters with express configuration does not support changing all settings at the time of create operations. For example, you can only choose Aurora standard storage when creating with express configuration. You can change the storage type after the cluster is created. See, Express configuration settings for a list of all other settings and default values that apply with express configuration. + * Clusters with express configuration does not support changing all settings at the time of create operations. For example, you can only choose Aurora Standard storage when creating with express configuration. You can change the storage type after the cluster is created. See, Express configuration settings for a list of all other settings and default values that apply with express configuration.