AWS AmazonRDS documentation change
Summary
Updated terminology from 'Aurora Serverless v2' to 'Aurora serverless' throughout the document, including section headers, instance references, and operational procedures. Removed 'v2' designation consistently.
Security assessment
The changes are purely branding/terminology updates without any security implications. No vulnerabilities, security configurations, or security features were modified or added. TLS/SSL content remains unchanged except for terminology updates.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2-administration.md b/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2-administration.md index dfc9cff34..55fafd303 100644 --- a//AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2-administration.md +++ b//AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2-administration.md @@ -7 +7 @@ -Setting the Aurora Serverless v2 capacity range for a clusterChecking the Aurora Serverless v2 capacity rangeChecking the Aurora Serverless v2 platform versionAdding an Aurora Serverless v2 readerConverting from provisioned to Aurora Serverless v2Converting from Aurora Serverless v2 to provisionedPausing Aurora Serverless v2 DB instancesChoosing the promotion tier for an Aurora Serverless v2 readerUsing TLS/SSL with Aurora Serverless v2Viewing Aurora Serverless v2 writers and readersLogging for Aurora Serverless v2 +Setting the Aurora serverless capacity range for a clusterChecking the Aurora serverless capacity rangeChecking the Aurora serverless platform versionAdding an Aurora serverless readerConverting from provisioned to Aurora serverlessConverting from Aurora serverless to provisionedPausing Aurora serverless DB instancesChoosing the promotion tier for an Aurora serverless readerUsing TLS/SSL with Aurora serverlessViewing Aurora serverless writers and readersLogging for Aurora serverless @@ -9 +9 @@ Setting the Aurora Serverless v2 capacity range for a clusterChecking the Aurora -# Managing Aurora Serverless v2 DB clusters +# Managing Aurora serverless DB clusters @@ -11 +11 @@ Setting the Aurora Serverless v2 capacity range for a clusterChecking the Aurora -With Aurora Serverless v2, your clusters are interchangeable with provisioned clusters. The Aurora Serverless v2 properties apply to one or more DB instances within a DB cluster. Thus, the procedures for creating clusters, modifying clusters, creating and restoring snapshots, and so on, are basically the same as for other kinds of Aurora clusters. For general procedures for managing Aurora clusters and DB instances, see [Managing an Amazon Aurora DB cluster](./CHAP_Aurora.html). +With Aurora serverless, your clusters are interchangeable with provisioned clusters. The Aurora serverless properties apply to one or more DB instances within a DB cluster. Thus, the procedures for creating clusters, modifying clusters, creating and restoring snapshots, and so on, are basically the same as for other kinds of Aurora clusters. For general procedures for managing Aurora clusters and DB instances, see [Managing an Amazon Aurora DB cluster](./CHAP_Aurora.html). @@ -13 +13 @@ With Aurora Serverless v2, your clusters are interchangeable with provisioned cl -In the following topics, you can learn about management considerations for clusters that contain Aurora Serverless v2 DB instances. +In the following topics, you can learn about management considerations for clusters that contain Aurora serverless DB instances. @@ -17 +17 @@ In the following topics, you can learn about management considerations for clust - * Setting the Aurora Serverless v2 capacity range for a cluster + * Setting the Aurora serverless capacity range for a cluster @@ -19 +19 @@ In the following topics, you can learn about management considerations for clust - * Checking the capacity range for Aurora Serverless v2 + * Checking the capacity range for Aurora serverless @@ -21 +21 @@ In the following topics, you can learn about management considerations for clust - * Checking the platform version for an existing Aurora Serverless v2 cluster + * Checking the platform version for an existing Aurora serverless cluster @@ -23 +23 @@ In the following topics, you can learn about management considerations for clust - * Adding an Aurora Serverless v2 reader + * Adding an Aurora serverless reader @@ -25 +25 @@ In the following topics, you can learn about management considerations for clust - * Converting a provisioned writer or reader to Aurora Serverless v2 + * Converting a provisioned writer or reader to Aurora serverless @@ -27 +27 @@ In the following topics, you can learn about management considerations for clust - * Converting an Aurora Serverless v2 writer or reader to provisioned + * Converting an Aurora serverless writer or reader to provisioned @@ -29 +29 @@ In the following topics, you can learn about management considerations for clust - * Pausing Aurora Serverless v2 DB instances + * Pausing Aurora serverless DB instances @@ -31 +31 @@ In the following topics, you can learn about management considerations for clust - * Choosing the promotion tier for an Aurora Serverless v2 reader + * Choosing the promotion tier for an Aurora serverless reader @@ -33 +33 @@ In the following topics, you can learn about management considerations for clust - * Using TLS/SSL with Aurora Serverless v2 + * Using TLS/SSL with Aurora serverless @@ -35 +35 @@ In the following topics, you can learn about management considerations for clust - * Viewing Aurora Serverless v2 writers and readers + * Viewing Aurora serverless writers and readers @@ -37 +37 @@ In the following topics, you can learn about management considerations for clust - * Logging for Aurora Serverless v2 + * Logging for Aurora serverless @@ -42 +42 @@ In the following topics, you can learn about management considerations for clust -## Setting the Aurora Serverless v2 capacity range for a cluster +## Setting the Aurora serverless capacity range for a cluster @@ -44 +44 @@ In the following topics, you can learn about management considerations for clust -To modify configuration parameters or other settings for clusters containing Aurora Serverless v2 DB instances, or the DB instances themselves, follow the same general procedures as for provisioned clusters. For details, see [Modifying an Amazon Aurora DB cluster](./Aurora.Modifying.html). +To modify configuration parameters or other settings for clusters containing Aurora serverless DB instances, or the DB instances themselves, follow the same general procedures as for provisioned clusters. For details, see [Modifying an Amazon Aurora DB cluster](./Aurora.Modifying.html). @@ -46 +46 @@ To modify configuration parameters or other settings for clusters containing Aur -The most important setting that's unique to Aurora Serverless v2 is the capacity range. After you set the minimum and maximum Aurora capacity unit (ACU) values for an Aurora cluster, you don't need to actively adjust the capacity of the Aurora Serverless v2 DB instances in the cluster. Aurora does that for you. This setting is managed at the cluster level. The same minimum and maximum ACU values apply to each Aurora Serverless v2 DB instance in the cluster. +The most important setting that's unique to Aurora serverless is the capacity range. After you set the minimum and maximum Aurora capacity unit (ACU) values for an Aurora cluster, you don't need to actively adjust the capacity of the Aurora serverless DB instances in the cluster. Aurora does that for you. This setting is managed at the cluster level. The same minimum and maximum ACU values apply to each Aurora serverless DB instance in the cluster. @@ -50 +50 @@ You can set the following specific values: - * **Minimum ACUs** – The Aurora Serverless v2 DB instance can reduce capacity down to this number of ACUs. + * **Minimum ACUs** – The Aurora serverless DB instance can reduce capacity down to this number of ACUs. @@ -52 +52 @@ You can set the following specific values: - * **Maximum ACUs** – The Aurora Serverless v2 DB instance can increase capacity up to this number of ACUs. + * **Maximum ACUs** – The Aurora serverless DB instance can increase capacity up to this number of ACUs. @@ -57 +57 @@ You can set the following specific values: -The available capacity range for Aurora Serverless v2 is a function of both the DB engine version and the platform version. Newer DB engine versions allow a maximum capacity of 256 ACUs, a minimum capacity of 0 ACUs, or both. For the capacity ranges for various DB engine versions, see [Aurora Serverless v2 capacity](./aurora-serverless-v2.how-it-works.html#aurora-serverless-v2.how-it-works.capacity). +The available capacity range for Aurora serverless is a function of both the DB engine version and the platform version. Newer DB engine versions allow a maximum capacity of 256 ACUs, a minimum capacity of 0 ACUs, or both. For the capacity ranges for various DB engine versions, see [Aurora serverless capacity](./aurora-serverless-v2.how-it-works.html#aurora-serverless-v2.how-it-works.capacity). @@ -59 +59 @@ The available capacity range for Aurora Serverless v2 is a function of both the -For the auto-pause and resume capability that's enabled by setting the minimum capacity to 0 ACUs, see [Scaling to Zero ACUs with automatic pause and resume for Aurora Serverless v2](./aurora-serverless-v2-auto-pause.html). +For the auto-pause and resume capability that's enabled by setting the minimum capacity to 0 ACUs, see [Scaling to Zero ACUs with automatic pause and resume for Aurora serverless](./aurora-serverless-v2-auto-pause.html). @@ -61 +61 @@ For the auto-pause and resume capability that's enabled by setting the minimum c -For more information on making sure that your Aurora Serverless v2 DB clusters can scale up to 256 ACUs, see Upgrading your Aurora Serverless v2 DB cluster to allow scaling to 256 ACUs. +For more information on making sure that your Aurora serverless DB clusters can scale up to 256 ACUs, see Upgrading your Aurora serverless DB cluster to allow scaling to 256 ACUs. @@ -65 +65 @@ For more information on making sure that your Aurora Serverless v2 DB clusters c -When you modify the capacity range for an Aurora Serverless v2 DB cluster, the change takes place immediately, regardless of whether you choose to apply it immediately or during the next scheduled maintenance window. +When you modify the capacity range for an Aurora serverless DB cluster, the change takes place immediately, regardless of whether you choose to apply it immediately or during the next scheduled maintenance window. @@ -67 +67 @@ When you modify the capacity range for an Aurora Serverless v2 DB cluster, the c -In Aurora Serverless v2, you can't directly set the current capacity without modifying the capacity range, as capacity dynamically adjusts based on the workload within the specified range. However, you can influence the capacity indirectly in the following ways: +In Aurora serverless, you can't directly set the current capacity without modifying the capacity range, as capacity dynamically adjusts based on the workload within the specified range. However, you can influence the capacity indirectly in the following ways: @@ -78 +78 @@ In Aurora Serverless v2, you can't directly set the current capacity without mod -For details about the effects of the capacity range and how to monitor and fine-tune it, see [Important Amazon CloudWatch metrics for Aurora Serverless v2](./aurora-serverless-v2.setting-capacity.html#aurora-serverless-v2.viewing.monitoring) and [Performance and scaling for Aurora Serverless v2](./aurora-serverless-v2.setting-capacity.html). Your goal is to make sure that the maximum capacity for the cluster is high enough to handle spikes in workload, and the minimum is low enough to minimize costs when the cluster isn't busy. +For details about the effects of the capacity range and how to monitor and fine-tune it, see [Important Amazon CloudWatch metrics for Aurora serverless](./aurora-serverless-v2.setting-capacity.html#aurora-serverless-v2.viewing.monitoring) and [Performance and scaling for Aurora serverless](./aurora-serverless-v2.setting-capacity.html). Your goal is to make sure that the maximum capacity for the cluster is high enough to handle spikes in workload, and the minimum is low enough to minimize costs when the cluster isn't busy. @@ -80 +80 @@ For details about the effects of the capacity range and how to monitor and fine- -Suppose that you determine based on your monitoring that the ACU range for the cluster should be higher, lower, wider, or narrower. You can set the capacity of an Aurora cluster to a specific range of ACUs with the AWS Management Console, the AWS CLI, or the Amazon RDS API. This capacity range applies to every Aurora Serverless v2 DB instance in the cluster. +Suppose that you determine based on your monitoring that the ACU range for the cluster should be higher, lower, wider, or narrower. You can set the capacity of an Aurora cluster to a specific range of ACUs with the AWS Management Console, the AWS CLI, or the Amazon RDS API. This capacity range applies to every Aurora serverless DB instance in the cluster. @@ -82 +82 @@ Suppose that you determine based on your monitoring that the ACU range for the c -For example, suppose that your cluster has a capacity range of 1–16 ACUs and contains two Aurora Serverless v2 DB instances. Then the cluster as a whole consumes somewhere between 2 ACUs (when idle) and 32 ACUs (when fully utilized). If you change the capacity range from 8 to 40.5 ACUs, now the entire cluster consumes 16 ACUs when idle, and up to 81 ACUs when fully utilized. +For example, suppose that your cluster has a capacity range of 1–16 ACUs and contains two Aurora serverless DB instances. Then the cluster as a whole consumes somewhere between 2 ACUs (when idle) and 32 ACUs (when fully utilized). If you change the capacity range from 8 to 40.5 ACUs, now the entire cluster consumes 16 ACUs when idle, and up to 81 ACUs when fully utilized. @@ -84 +84 @@ For example, suppose that your cluster has a capacity range of 1–16 ACUs and c -Aurora automatically sets certain parameters for Aurora Serverless v2 DB instances to values that depend on the maximum ACU value in the capacity range. For the list of such parameters, see [Maximum connections for Aurora Serverless v2](./aurora-serverless-v2.setting-capacity.html#aurora-serverless-v2.max-connections). For static parameters that rely on this type of calculation, the value is evaluated again when you reboot the DB instance. Thus, you can update the value of such parameters by rebooting the DB instance after changing the capacity range. To check whether you need to reboot your DB instance to pick up such parameter changes, check the `ParameterApplyStatus` attribute of the DB instance. A value of `pending-reboot` indicates that rebooting will apply changes to some parameter values. +Aurora automatically sets certain parameters for Aurora serverless DB instances to values that depend on the maximum ACU value in the capacity range. For the list of such parameters, see [Maximum connections for Aurora serverless](./aurora-serverless-v2.setting-capacity.html#aurora-serverless-v2.max-connections). For static parameters that rely on this type of calculation, the value is evaluated again when you reboot the DB instance. Thus, you can update the value of such parameters by rebooting the DB instance after changing the capacity range. To check whether you need to reboot your DB instance to pick up such parameter changes, check the `ParameterApplyStatus` attribute of the DB instance. A value of `pending-reboot` indicates that rebooting will apply changes to some parameter values. @@ -86 +86 @@ Aurora automatically sets certain parameters for Aurora Serverless v2 DB instanc -You can set the capacity range of a cluster that contains Aurora Serverless v2 DB instances with the AWS Management Console. +You can set the capacity range of a cluster that contains Aurora serverless DB instances with the AWS Management Console. @@ -88 +88 @@ You can set the capacity range of a cluster that contains Aurora Serverless v2 D -When you use the console, you set the capacity range for the cluster at the time that you add the first Aurora Serverless v2 DB instance to that cluster. You might do so when you choose the **Serverless v2** DB instance class for the writer DB instance when you create the cluster. Or you might do so when you choose the **Serverless** DB instance class when you add an Aurora Serverless v2 reader DB instance to the cluster. Or you might do so when you convert an existing provisioned DB instance in the cluster to the **Serverless** DB instance class. For the full versions of those procedures, see [Creating an Aurora Serverless v2 writer DB instance](./aurora-serverless-v2.create.html#aurora-serverless-v2-adding-writer), Adding an Aurora Serverless v2 reader, and Converting a provisioned writer or reader to Aurora Serverless v2. +When you use the console, you set the capacity range for the cluster at the time that you add the first Aurora serverless DB instance to that cluster. You might do so when you choose the **Serverless v2** DB instance class for the writer DB instance when you create the cluster. Or you might do so when you choose the **Serverless** DB instance class when you add an Aurora serverless reader DB instance to the cluster. Or you might do so when you convert an existing provisioned DB instance in the cluster to the **Serverless** DB instance class. For the full versions of those procedures, see [Creating an Aurora serverless writer DB instance](./aurora-serverless-v2.create.html#aurora-serverless-v2-adding-writer), Adding an Aurora serverless reader, and Converting a provisioned writer or reader to Aurora serverless. @@ -90 +90 @@ When you use the console, you set the capacity range for the cluster at the time -Whatever capacity range that you set at the cluster level applies to all Aurora Serverless v2 DB instances in your cluster. The following image shows a cluster with multiple Aurora Serverless v2 reader DB instances. Each has an identical capacity range of 2–64 ACUs. +Whatever capacity range that you set at the cluster level applies to all Aurora serverless DB instances in your cluster. The following image shows a cluster with multiple Aurora serverless reader DB instances. Each has an identical capacity range of 2–64 ACUs. @@ -92 +92 @@ Whatever capacity range that you set at the cluster level applies to all Aurora - + @@ -94 +94 @@ Whatever capacity range that you set at the cluster level applies to all Aurora -###### To modify the capacity range of an Aurora Serverless v2 cluster +###### To modify the capacity range of an Aurora serverless cluster @@ -100 +100 @@ Whatever capacity range that you set at the cluster level applies to all Aurora - 3. Choose the cluster containing your Aurora Serverless v2 DB instances from the list. The cluster must already contain at least one Aurora Serverless v2 DB instance. Otherwise, Aurora doesn't show the **Capacity range** section. + 3. Choose the cluster containing your Aurora serverless DB instances from the list. The cluster must already contain at least one Aurora serverless DB instance. Otherwise, Aurora doesn't show the **Capacity range** section. @@ -123 +123 @@ The capacity modification takes place immediately, regardless of whether you cho -To set the capacity of a cluster where you intend to use Aurora Serverless v2 DB instances using the AWS CLI, run the [modify-db-cluster](https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-cluster.html) AWS CLI command. Specify the `--serverless-v2-scaling-configuration` option. The cluster might already contain one or more Aurora Serverless v2 DB instances, or you can add the DB instances later. Valid values for the `MinCapacity` and `MaxCapacity` fields include the following: +To set the capacity of a cluster where you intend to use Aurora serverless DB instances using the AWS CLI, run the [modify-db-cluster](https://docs.aws.amazon.com/cli/latest/reference/rds/modify-db-cluster.html) AWS CLI command. Specify the `--serverless-v2-scaling-configuration` option. The cluster might already contain one or more Aurora serverless DB instances, or you can add the DB instances later. Valid values for the `MinCapacity` and `MaxCapacity` fields include the following: @@ -141 +141 @@ The capacity modification takes place immediately, regardless of whether you cho -After doing so, you can add Aurora Serverless v2 DB instances to the cluster and each new DB instance can scale between 48.5 and 64 ACUs. The new capacity range also applies to any Aurora Serverless v2 DB instances that were already in the cluster. The DB instances scale up or down if necessary to fall within the new capacity range. +After doing so, you can add Aurora serverless DB instances to the cluster and each new DB instance can scale between 48.5 and 64 ACUs. The new capacity range also applies to any Aurora serverless DB instances that were already in the cluster. The DB instances scale up or down if necessary to fall within the new capacity range. @@ -143 +143 @@ After doing so, you can add Aurora Serverless v2 DB instances to the cluster and -For additional examples of setting the capacity range using the CLI, see [Choosing the Aurora Serverless v2 capacity range for an Aurora cluster](./aurora-serverless-v2.setting-capacity.html#aurora-serverless-v2-examples-setting-capacity-range-for-cluster). +For additional examples of setting the capacity range using the CLI, see [Choosing the Aurora serverless capacity range for an Aurora cluster](./aurora-serverless-v2.setting-capacity.html#aurora-serverless-v2-examples-setting-capacity-range-for-cluster). @@ -156 +156 @@ To modify the scaling configuration of an Aurora Serverless DB cluster using the -In the following example, you modify the scaling configuration of an Aurora Serverless v2 DB instance named `sample-instance` that's part of a cluster named `sample-cluster`. +In the following example, you modify the scaling configuration of an Aurora serverless DB instance named `sample-instance` that's part of a cluster named `sample-cluster`. @@ -179 +179 @@ You can set the capacity of an Aurora DB instance with the [ModifyDBCluster](htt -You can modify the scaling configuration of a cluster containing Aurora Serverless v2 DB instances with the [ModifyDBCluster](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyDBCluster.html) API operation. Specify the `ServerlessV2ScalingConfiguration` parameter to configure the minimum capacity and the maximum capacity. Valid capacity values include the following: +You can modify the scaling configuration of a cluster containing Aurora serverless DB instances with the [ModifyDBCluster](https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_ModifyDBCluster.html) API operation. Specify the `ServerlessV2ScalingConfiguration` parameter to configure the minimum capacity and the maximum capacity. Valid capacity values include the following: @@ -194 +194 @@ The capacity modification takes place immediately, regardless of whether you cho -### Upgrading your Aurora Serverless v2 DB cluster to allow scaling to 256 ACUs +### Upgrading your Aurora serverless DB cluster to allow scaling to 256 ACUs @@ -196 +196 @@ The capacity modification takes place immediately, regardless of whether you cho -In some cases, when you try to scale your Aurora Serverless v2 DB cluster to capacities greater than 128 ACUs, you receive an error message. The error message tells you which instances are incompatible with the new scaling range. This highlights the important relationship between your capacity range, DB engine version, and platform version. +In some cases, when you try to scale your Aurora serverless DB cluster to capacities greater than 128 ACUs, you receive an error message. The error message tells you which instances are incompatible with the new scaling range. This highlights the important relationship between your capacity range, DB engine version, and platform version. @@ -200 +200 @@ The inability to scale greater than 128 ACUs can happen for one of two reasons: - * Older DB engine version – Upgrade the DB engine version to one that supports 256 ACUs. For more information, see [Aurora Serverless v2 capacity](./aurora-serverless-v2.how-it-works.html#aurora-serverless-v2.how-it-works.capacity). + * Older DB engine version – Upgrade the DB engine version to one that supports 256 ACUs. For more information, see [Aurora serverless capacity](./aurora-serverless-v2.how-it-works.html#aurora-serverless-v2.how-it-works.capacity). @@ -202 +202 @@ The inability to scale greater than 128 ACUs can happen for one of two reasons: - * Older platform version – Upgrade the platform for your Aurora Serverless v2 DB cluster. You can do this in one of the following ways: + * Older platform version – Upgrade the platform for your Aurora serverless DB cluster. You can do this in one of the following ways: @@ -229 +229 @@ However, stopping and starting a DB cluster incurs some downtime, usually severa -## Checking the capacity range for Aurora Serverless v2 +## Checking the capacity range for Aurora serverless @@ -231 +231 @@ However, stopping and starting a DB cluster incurs some downtime, usually severa -The procedure to check the capacity range for your Aurora Serverless v2 cluster requires that you first set a capacity range. If you haven't done so, follow the procedure in Setting the Aurora Serverless v2 capacity range for a cluster. +The procedure to check the capacity range for your Aurora serverless cluster requires that you first set a capacity range. If you haven't done so, follow the procedure in Setting the Aurora serverless capacity range for a cluster. @@ -233 +233 @@ The procedure to check the capacity range for your Aurora Serverless v2 cluster -Whatever capacity range you set at the cluster level applies to all Aurora Serverless v2 DB instances in your cluster. The following image shows a cluster with multiple Aurora Serverless v2 DB instances. Each has an identical capacity range. +Whatever capacity range you set at the cluster level applies to all Aurora serverless DB instances in your cluster. The following image shows a cluster with multiple Aurora serverless DB instances. Each has an identical capacity range. @@ -235 +235 @@ Whatever capacity range you set at the cluster level applies to all Aurora Serve - + @@ -237 +237 @@ Whatever capacity range you set at the cluster level applies to all Aurora Serve -You can also view the details page for any Aurora Serverless v2 DB instance in the cluster. DB instances' capacity range appears on the **Configuration** tab. +You can also view the details page for any Aurora serverless DB instance in the cluster. DB instances' capacity range appears on the **Configuration** tab. @@ -241 +241 @@ You can also view the details page for any Aurora Serverless v2 DB instance in t -You can also see the current capacity range for the cluster on the **Modify** page for the cluster. At that point, you can change the capacity range. For all the ways that you can set or change the capacity range, see Setting the Aurora Serverless v2 capacity range for a cluster. +You can also see the current capacity range for the cluster on the **Modify** page for the cluster. At that point, you can change the capacity range. For all the ways that you can set or change the capacity range, see Setting the Aurora serverless capacity range for a cluster. @@ -245 +245 @@ You can also see the current capacity range for the cluster on the **Modify** pa -You can check the capacity range that's configured for Aurora Serverless v2 DB instances in a cluster by examining the `ServerlessV2ScalingConfiguration` attribute for the cluster. The following AWS CLI example shows a cluster with a minimum capacity of 0.5 Aurora capacity units (ACUs) and a maximum capacity of 16 ACUs. +You can check the capacity range that's configured for Aurora serverless DB instances in a cluster by examining the `ServerlessV2ScalingConfiguration` attribute for the cluster. The following AWS CLI example shows a cluster with a minimum capacity of 0.5 Aurora capacity units (ACUs) and a maximum capacity of 16 ACUs. @@ -259 +259 @@ You can check the capacity range that's configured for Aurora Serverless v2 DB i -## Checking the platform version for an existing Aurora Serverless v2 cluster +## Checking the platform version for an existing Aurora serverless cluster @@ -318 +318 @@ You can use the `describe-serverless-v2-platform-versions` command to check the -You can use the `describe-pending-maintenance-actions` command to check whether there are any pending platform version upgrades for your Aurora Serverless v2 DB clusters. +You can use the `describe-pending-maintenance-actions` command to check whether there are any pending platform version upgrades for your Aurora serverless DB clusters. @@ -335 +335 @@ To schedule a platform version upgrade, specify the following parameters: - * `--resource-identifier` – The ARN of your Aurora Serverless v2 DB cluster + * `--resource-identifier` – The ARN of your Aurora serverless DB cluster @@ -348 +348 @@ To schedule a platform version upgrade, specify the following parameters: -## Adding an Aurora Serverless v2 reader +## Adding an Aurora serverless reader @@ -350 +350 @@ To schedule a platform version upgrade, specify the following parameters: -To add an Aurora Serverless v2 reader DB instance to your cluster, you follow the same general procedure as in [Adding Aurora Replicas to a DB cluster](./aurora-replicas-adding.html). Choose the **Serverless v2** instance class for the new DB instance. +To add an Aurora serverless reader DB instance to your cluster, you follow the same general procedure as in [Adding Aurora Replicas to a DB cluster](./aurora-replicas-adding.html). Choose the **Serverless v2** instance class for the new DB instance. @@ -352 +352 @@ To add an Aurora Serverless v2 reader DB instance to your cluster, you follow th -If the reader DB instance is the first Aurora Serverless v2 DB instance in the cluster, you also choose the capacity range. This setting applies to this reader DB instance and to any other Aurora Serverless v2 DB instances that you add to the cluster. Each Aurora Serverless v2 DB instance can scale between the minimum and maximum ACU values. +If the reader DB instance is the first Aurora serverless DB instance in the cluster, you also choose the capacity range. This setting applies to this reader DB instance and to any other Aurora serverless DB instances that you add to the cluster. Each Aurora serverless DB instance can scale between the minimum and maximum ACU values. @@ -354 +354 @@ If the reader DB instance is the first Aurora Serverless v2 DB instance in the c -If any other Aurora Serverless v2 instances already exist in the cluster, the **Add reader** dialog shows the current capacity range for the cluster. In that case, you can't change the capacity. The following image shows the report of the current cluster capacity. +If any other Aurora serverless instances already exist in the cluster, the **Add reader** dialog shows the current capacity range for the cluster. In that case, you can't change the capacity. The following image shows the report of the current cluster capacity. @@ -356 +356 @@ If any other Aurora Serverless v2 instances already exist in the cluster, the ** - + @@ -358 +358 @@ If any other Aurora Serverless v2 instances already exist in the cluster, the ** -If you already added any Aurora Serverless v2 DB instances to the cluster, adding another Aurora Serverless v2 reader DB instance shows you the current capacity range. The following image shows those read-only controls. +If you already added any Aurora serverless DB instances to the cluster, adding another Aurora serverless reader DB instance shows you the current capacity range. The following image shows those read-only controls. @@ -360 +360 @@ If you already added any Aurora Serverless v2 DB instances to the cluster, addin - + @@ -362 +362 @@ If you already added any Aurora Serverless v2 DB instances to the cluster, addin -If you want to change the capacity range for the cluster, follow the procedure in Setting the Aurora Serverless v2 capacity range for a cluster. +If you want to change the capacity range for the cluster, follow the procedure in Setting the Aurora serverless capacity range for a cluster. @@ -364 +364 @@ If you want to change the capacity range for the cluster, follow the procedure i -For clusters containing more than one reader DB instance, the failover priority of each Aurora Serverless v2 reader DB instance plays an important part in how that DB instance scales up and down. You can't specify the priority when you initially create the cluster. Keep this property in mind when you add a second reader or later DB instance to your cluster. For more information, see Choosing the promotion tier for an Aurora Serverless v2 reader. +For clusters containing more than one reader DB instance, the failover priority of each Aurora serverless reader DB instance plays an important part in how that DB instance scales up and down. You can't specify the priority when you initially create the cluster. Keep this property in mind when you add a second reader or later DB instance to your cluster. For more information, see Choosing the promotion tier for an Aurora serverless reader. @@ -366 +366 @@ For clusters containing more than one reader DB instance, the failover priority -For other ways that you can see the current capacity range for a cluster, see Checking the capacity range for Aurora Serverless v2. +For other ways that you can see the current capacity range for a cluster, see Checking the capacity range for Aurora serverless. @@ -368 +368 @@ For other ways that you can see the current capacity range for a cluster, see Ch -## Converting a provisioned writer or reader to Aurora Serverless v2 +## Converting a provisioned writer or reader to Aurora serverless @@ -370 +370 @@ For other ways that you can see the current capacity range for a cluster, see Ch