diff --git a/clients/client-elasticache/src/commands/AddTagsToResourceCommand.ts b/clients/client-elasticache/src/commands/AddTagsToResourceCommand.ts index 6d8fface5286..105326485423 100644 --- a/clients/client-elasticache/src/commands/AddTagsToResourceCommand.ts +++ b/clients/client-elasticache/src/commands/AddTagsToResourceCommand.ts @@ -31,13 +31,13 @@ export interface AddTagsToResourceCommandOutput extends TagListMessage, __Metada *

A tag is a key-value pair where the key and value are case-sensitive. You can use tags * to categorize and track all your ElastiCache resources, with the exception of global * replication group. When you add or remove tags on replication groups, those actions will - * be replicated to all nodes in the replication group. For more information, see Resource-level permissions.

+ * be replicated to all nodes in the replication group. For more information, see Resource-level permissions.

*

For example, you can use cost-allocation tags to your ElastiCache resources, Amazon * generates a cost allocation report as a comma-separated value (CSV) file with your usage * and costs aggregated by your tags. You can apply tags that represent business categories * (such as cost centers, application names, or owners) to organize your costs across * multiple services.

- *

For more information, see Using Cost Allocation Tags in + *

For more information, see Using Cost Allocation Tags in * Amazon ElastiCache in the ElastiCache User * Guide.

* @example diff --git a/clients/client-elasticache/src/commands/BatchApplyUpdateActionCommand.ts b/clients/client-elasticache/src/commands/BatchApplyUpdateActionCommand.ts index daa168310d39..ec0e5139cd46 100644 --- a/clients/client-elasticache/src/commands/BatchApplyUpdateActionCommand.ts +++ b/clients/client-elasticache/src/commands/BatchApplyUpdateActionCommand.ts @@ -29,7 +29,7 @@ export interface BatchApplyUpdateActionCommandOutput extends UpdateActionResults /** *

Apply the service update. For more information on service updates and applying them, - * see Applying Service + * see Applying Service * Updates.

* @example * Use a bare-bones client and the command you need to make an API call. diff --git a/clients/client-elasticache/src/commands/BatchStopUpdateActionCommand.ts b/clients/client-elasticache/src/commands/BatchStopUpdateActionCommand.ts index 4c9582a3a78a..d8cd50c6dbc1 100644 --- a/clients/client-elasticache/src/commands/BatchStopUpdateActionCommand.ts +++ b/clients/client-elasticache/src/commands/BatchStopUpdateActionCommand.ts @@ -29,7 +29,7 @@ export interface BatchStopUpdateActionCommandOutput extends UpdateActionResultsM /** *

Stop the service update. For more information on service updates and stopping them, - * see Stopping + * see Stopping * Service Updates.

* @example * Use a bare-bones client and the command you need to make an API call. diff --git a/clients/client-elasticache/src/commands/CopySnapshotCommand.ts b/clients/client-elasticache/src/commands/CopySnapshotCommand.ts index ac758968c552..6ab21d7b2783 100644 --- a/clients/client-elasticache/src/commands/CopySnapshotCommand.ts +++ b/clients/client-elasticache/src/commands/CopySnapshotCommand.ts @@ -37,8 +37,8 @@ export interface CopySnapshotCommandOutput extends CopySnapshotResult, __Metadat * operation can create their own Amazon S3 buckets and copy snapshots to it. To * control access to your snapshots, use an IAM policy to control who has the ability * to use the CopySnapshot operation. For more information about using IAM - * to control the use of ElastiCache operations, see Exporting - * Snapshots and Authentication & Access + * to control the use of ElastiCache operations, see Exporting + * Snapshots and Authentication & Access * Control.

* *

You could receive the following error messages.

@@ -52,7 +52,7 @@ export interface CopySnapshotCommandOutput extends CopySnapshotResult, __Metadat * the region.

*

* Solution: Create an Amazon S3 bucket in the - * same region as your snapshot. For more information, see Step 1: Create an Amazon S3 Bucket in the ElastiCache User + * same region as your snapshot. For more information, see Step 1: Create an Amazon S3 Bucket in the ElastiCache User * Guide.

* *
  • @@ -61,7 +61,7 @@ export interface CopySnapshotCommandOutput extends CopySnapshotResult, __Metadat * exist.

    *

    * Solution: Create an Amazon S3 bucket in the - * same region as your snapshot. For more information, see Step 1: Create an Amazon S3 Bucket in the ElastiCache User + * same region as your snapshot. For more information, see Step 1: Create an Amazon S3 Bucket in the ElastiCache User * Guide.

    *
    • *
  • @@ -70,7 +70,7 @@ export interface CopySnapshotCommandOutput extends CopySnapshotResult, __Metadat * by the authenticated user.

    *

    * Solution: Create an Amazon S3 bucket in the - * same region as your snapshot. For more information, see Step 1: Create an Amazon S3 Bucket in the ElastiCache User + * same region as your snapshot. For more information, see Step 1: Create an Amazon S3 Bucket in the ElastiCache User * Guide.

    *
    • *
  • @@ -97,7 +97,7 @@ export interface CopySnapshotCommandOutput extends CopySnapshotResult, __Metadat * granted READ permissions %s on the S3 Bucket.

    *

    * Solution: Add List and Read permissions on - * the bucket. For more information, see Step 2: Grant ElastiCache Access to Your Amazon S3 Bucket in the + * the bucket. For more information, see Step 2: Grant ElastiCache Access to Your Amazon S3 Bucket in the * ElastiCache User Guide.

    *
    • *
  • @@ -106,7 +106,7 @@ export interface CopySnapshotCommandOutput extends CopySnapshotResult, __Metadat * granted WRITE permissions %s on the S3 Bucket.

    *

    * Solution: Add Upload/Delete permissions on - * the bucket. For more information, see Step 2: Grant ElastiCache Access to Your Amazon S3 Bucket in the + * the bucket. For more information, see Step 2: Grant ElastiCache Access to Your Amazon S3 Bucket in the * ElastiCache User Guide.

    *
    • *
  • @@ -115,7 +115,7 @@ export interface CopySnapshotCommandOutput extends CopySnapshotResult, __Metadat * granted READ_ACP permissions %s on the S3 Bucket.

    *

    * Solution: Add View Permissions on the bucket. - * For more information, see Step 2: Grant ElastiCache Access to Your Amazon S3 Bucket in the + * For more information, see Step 2: Grant ElastiCache Access to Your Amazon S3 Bucket in the * ElastiCache User Guide.

    *
    • * diff --git a/clients/client-elasticache/src/commands/CreateCacheClusterCommand.ts b/clients/client-elasticache/src/commands/CreateCacheClusterCommand.ts index 150d8ef53a23..ef7aea2bfc95 100644 --- a/clients/client-elasticache/src/commands/CreateCacheClusterCommand.ts +++ b/clients/client-elasticache/src/commands/CreateCacheClusterCommand.ts @@ -245,7 +245,7 @@ export interface CreateCacheClusterCommandOutput extends CreateCacheClusterResul * * @throws {@link InsufficientCacheClusterCapacityFault} (client fault) *

    The requested cache node type is not available in the specified Availability Zone. For - * more information, see InsufficientCacheClusterCapacity in the ElastiCache User Guide.

    + * more information, see InsufficientCacheClusterCapacity in the ElastiCache User Guide.

    * * @throws {@link InvalidParameterCombinationException} (client fault) *

    Two or more incompatible parameters were specified.

    diff --git a/clients/client-elasticache/src/commands/CreateCacheParameterGroupCommand.ts b/clients/client-elasticache/src/commands/CreateCacheParameterGroupCommand.ts index f578ce8aad66..f01dddcd1624 100644 --- a/clients/client-elasticache/src/commands/CreateCacheParameterGroupCommand.ts +++ b/clients/client-elasticache/src/commands/CreateCacheParameterGroupCommand.ts @@ -42,7 +42,7 @@ export interface CreateCacheParameterGroupCommandOutput extends CreateCacheParam * *
  • *

    - * Parameters and + * Parameters and * Parameter Groups in the ElastiCache User Guide.

    *
    • * diff --git a/clients/client-elasticache/src/commands/CreateGlobalReplicationGroupCommand.ts b/clients/client-elasticache/src/commands/CreateGlobalReplicationGroupCommand.ts index 4fd911d3b898..ff9c597ea4db 100644 --- a/clients/client-elasticache/src/commands/CreateGlobalReplicationGroupCommand.ts +++ b/clients/client-elasticache/src/commands/CreateGlobalReplicationGroupCommand.ts @@ -33,7 +33,7 @@ export interface CreateGlobalReplicationGroupCommandOutput *

    Global Datastore offers fully managed, fast, reliable and secure * cross-region replication. Using Global Datastore with Valkey or Redis OSS, you can create cross-region * read replica clusters for ElastiCache to enable low-latency reads and disaster - * recovery across regions. For more information, see Replication + * recovery across regions. For more information, see Replication * Across Regions Using Global Datastore.

    * - *

    For more information, see Authenticating Users with AUTH + *

    For more information, see Authenticating Users with AUTH *

    * @public */ @@ -11162,7 +11162,7 @@ export interface ModifyReplicationGroupMessage { * group.

    *

    * Important: You can upgrade to a newer engine version - * (see Selecting + * (see Selecting * a Cache Engine and Version), but you cannot downgrade to an earlier engine * version. If you want to use an earlier engine version, you must delete the existing * replication group and create it anew with the earlier engine version.

    @@ -11242,7 +11242,7 @@ export interface ModifyReplicationGroupMessage { *

    DELETE - allowed only when transitioning to RBAC

    * * - *

    For more information, see Authenticating Users with AUTH + *

    For more information, see Authenticating Users with AUTH *

    * @public */ @@ -11526,6 +11526,12 @@ export interface ModifyUserMessage { * @public */ AuthenticationMode?: AuthenticationMode | undefined; + + /** + *

    The engine for a specific user.

    + * @public + */ + Engine?: string | undefined; } /** @@ -11549,6 +11555,12 @@ export interface ModifyUserGroupMessage { * @public */ UserIdsToRemove?: string[] | undefined; + + /** + *

    The engine for a user group.

    + * @public + */ + Engine?: string | undefined; } /** diff --git a/clients/client-elasticache/src/protocols/Aws_query.ts b/clients/client-elasticache/src/protocols/Aws_query.ts index da2374444ba3..6ef9e3e4cb69 100644 --- a/clients/client-elasticache/src/protocols/Aws_query.ts +++ b/clients/client-elasticache/src/protocols/Aws_query.ts @@ -7299,6 +7299,9 @@ const se_ModifyUserGroupMessage = (input: ModifyUserGroupMessage, context: __Ser entries[loc] = value; }); } + if (input[_E] != null) { + entries[_E] = input[_E]; + } return entries; }; @@ -7336,6 +7339,9 @@ const se_ModifyUserMessage = (input: ModifyUserMessage, context: __SerdeContext) entries[loc] = value; }); } + if (input[_E] != null) { + entries[_E] = input[_E]; + } return entries; }; diff --git a/codegen/sdk-codegen/aws-models/elasticache.json b/codegen/sdk-codegen/aws-models/elasticache.json index 050fc86de602..f4e70dd4f19c 100644 --- a/codegen/sdk-codegen/aws-models/elasticache.json +++ b/codegen/sdk-codegen/aws-models/elasticache.json @@ -128,7 +128,7 @@ } ], "traits": { - "smithy.api#documentation": "

    A tag is a key-value pair where the key and value are case-sensitive. You can use tags\n to categorize and track all your ElastiCache resources, with the exception of global\n replication group. When you add or remove tags on replication groups, those actions will\n be replicated to all nodes in the replication group. For more information, see Resource-level permissions.

    \n

    For example, you can use cost-allocation tags to your ElastiCache resources, Amazon\n generates a cost allocation report as a comma-separated value (CSV) file with your usage\n and costs aggregated by your tags. You can apply tags that represent business categories\n (such as cost centers, application names, or owners) to organize your costs across\n multiple services.

    \n

    For more information, see Using Cost Allocation Tags in\n Amazon ElastiCache in the ElastiCache User\n Guide.

    ", + "smithy.api#documentation": "

    A tag is a key-value pair where the key and value are case-sensitive. You can use tags\n to categorize and track all your ElastiCache resources, with the exception of global\n replication group. When you add or remove tags on replication groups, those actions will\n be replicated to all nodes in the replication group. For more information, see Resource-level permissions.

    \n

    For example, you can use cost-allocation tags to your ElastiCache resources, Amazon\n generates a cost allocation report as a comma-separated value (CSV) file with your usage\n and costs aggregated by your tags. You can apply tags that represent business categories\n (such as cost centers, application names, or owners) to organize your costs across\n multiple services.

    \n

    For more information, see Using Cost Allocation Tags in\n Amazon ElastiCache in the ElastiCache User\n Guide.

    ", "smithy.api#examples": [ { "title": "AddTagsToResource", @@ -1777,7 +1777,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Apply the service update. For more information on service updates and applying them,\n see Applying Service\n Updates.

    " + "smithy.api#documentation": "

    Apply the service update. For more information on service updates and applying them,\n see Applying Service\n Updates.

    " } }, "com.amazonaws.elasticache#BatchApplyUpdateActionMessage": { @@ -1825,7 +1825,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Stop the service update. For more information on service updates and stopping them,\n see Stopping\n Service Updates.

    " + "smithy.api#documentation": "

    Stop the service update. For more information on service updates and stopping them,\n see Stopping\n Service Updates.

    " } }, "com.amazonaws.elasticache#BatchStopUpdateActionMessage": { @@ -1886,7 +1886,7 @@ "CacheNodeType": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The name of the compute and memory capacity node type for the cluster.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " + "smithy.api#documentation": "

    The name of the compute and memory capacity node type for the cluster.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " } }, "Engine": { @@ -2262,7 +2262,7 @@ } }, "traits": { - "smithy.api#documentation": "

    Represents an individual cache node within a cluster. Each cache node runs its own\n instance of the cluster's protocol-compliant caching software - either Memcached, Valkey or Redis OSS.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " + "smithy.api#documentation": "

    Represents an individual cache node within a cluster. Each cache node runs its own\n instance of the cluster's protocol-compliant caching software - either Memcached, Valkey or Redis OSS.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " } }, "com.amazonaws.elasticache#CacheNodeIdsList": { @@ -2337,7 +2337,7 @@ "ChangeType": { "target": "com.amazonaws.elasticache#ChangeType", "traits": { - "smithy.api#documentation": "

    Indicates whether a change to the parameter is applied immediately or requires a\n reboot for the change to be applied. You can force a reboot or wait until the next\n maintenance window's reboot. For more information, see Rebooting a\n Cluster.

    " + "smithy.api#documentation": "

    Indicates whether a change to the parameter is applied immediately or requires a\n reboot for the change to be applied. You can force a reboot or wait until the next\n maintenance window's reboot. For more information, see Rebooting a\n Cluster.

    " } } }, @@ -3109,7 +3109,7 @@ "target": "com.amazonaws.elasticache#AllowedNodeGroupId", "traits": { "smithy.api#clientOptional": {}, - "smithy.api#documentation": "

    The 4-digit id for the node group you are configuring. For Valkey or Redis OSS (cluster mode\n disabled) replication groups, the node group id is always 0001. To find a Valkey or Redis OSS (cluster mode enabled)'s node group's (shard's) id, see Finding a Shard's\n Id.

    ", + "smithy.api#documentation": "

    The 4-digit id for the node group you are configuring. For Valkey or Redis OSS (cluster mode\n disabled) replication groups, the node group id is always 0001. To find a Valkey or Redis OSS (cluster mode enabled)'s node group's (shard's) id, see Finding a Shard's\n Id.

    ", "smithy.api#required": {} } }, @@ -3258,7 +3258,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Makes a copy of an existing snapshot.

    \n \n

    This operation is valid for Valkey or Redis OSS only.

    \n     \n \n

    Users or groups that have permissions to use the CopySnapshot\n operation can create their own Amazon S3 buckets and copy snapshots to it. To\n control access to your snapshots, use an IAM policy to control who has the ability\n to use the CopySnapshot operation. For more information about using IAM\n to control the use of ElastiCache operations, see Exporting\n Snapshots and Authentication & Access\n Control.

    \n     \n

    You could receive the following error messages.

    \n

    \n Error Messages\n

    \n ", + "smithy.api#documentation": "

    Makes a copy of an existing snapshot.

    \n \n

    This operation is valid for Valkey or Redis OSS only.

    \n     \n \n

    Users or groups that have permissions to use the CopySnapshot\n operation can create their own Amazon S3 buckets and copy snapshots to it. To\n control access to your snapshots, use an IAM policy to control who has the ability\n to use the CopySnapshot operation. For more information about using IAM\n to control the use of ElastiCache operations, see Exporting\n Snapshots and Authentication & Access\n Control.

    \n     \n

    You could receive the following error messages.

    \n

    \n Error Messages\n

    \n ", "smithy.api#examples": [ { "title": "CopySnapshot", @@ -3324,7 +3324,7 @@ "TargetBucket": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The Amazon S3 bucket to which the snapshot is exported. This parameter is used only\n when exporting a snapshot for external access.

    \n

    When using this parameter to export a snapshot, be sure Amazon ElastiCache has the\n needed permissions to this S3 bucket. For more information, see Step 2: Grant ElastiCache Access to Your Amazon S3 Bucket in the\n Amazon ElastiCache User Guide.

    \n

    For more information, see Exporting a\n Snapshot in the Amazon ElastiCache User Guide.

    " + "smithy.api#documentation": "

    The Amazon S3 bucket to which the snapshot is exported. This parameter is used only\n when exporting a snapshot for external access.

    \n

    When using this parameter to export a snapshot, be sure Amazon ElastiCache has the\n needed permissions to this S3 bucket. For more information, see Step 2: Grant ElastiCache Access to Your Amazon S3 Bucket in the\n Amazon ElastiCache User Guide.

    \n

    For more information, see Exporting a\n Snapshot in the Amazon ElastiCache User Guide.

    " } }, "KmsKeyId": { @@ -3534,7 +3534,7 @@ "CacheNodeType": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The compute and memory capacity of the nodes in the node group (shard).

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " + "smithy.api#documentation": "

    The compute and memory capacity of the nodes in the node group (shard).

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " } }, "Engine": { @@ -3546,7 +3546,7 @@ "EngineVersion": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The version number of the cache engine to be used for this cluster. To view the\n supported cache engine versions, use the DescribeCacheEngineVersions operation.

    \n

    \n Important: You can upgrade to a newer engine version\n (see Selecting\n a Cache Engine and Version), but you cannot downgrade to an earlier engine\n version. If you want to use an earlier engine version, you must delete the existing\n cluster or replication group and create it anew with the earlier engine version.

    " + "smithy.api#documentation": "

    The version number of the cache engine to be used for this cluster. To view the\n supported cache engine versions, use the DescribeCacheEngineVersions operation.

    \n

    \n Important: You can upgrade to a newer engine version\n (see Selecting\n a Cache Engine and Version), but you cannot downgrade to an earlier engine\n version. If you want to use an earlier engine version, you must delete the existing\n cluster or replication group and create it anew with the earlier engine version.

    " } }, "CacheParameterGroupName": { @@ -3558,7 +3558,7 @@ "CacheSubnetGroupName": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The name of the subnet group to be used for the cluster.

    \n

    Use this parameter only when you are creating a cluster in an Amazon Virtual Private\n Cloud (Amazon VPC).

    \n \n

    If you're going to launch your cluster in an Amazon VPC, you need to create a\n subnet group before you start creating a cluster. For more information, see Subnets and Subnet Groups.

    \n     " + "smithy.api#documentation": "

    The name of the subnet group to be used for the cluster.

    \n

    Use this parameter only when you are creating a cluster in an Amazon Virtual Private\n Cloud (Amazon VPC).

    \n \n

    If you're going to launch your cluster in an Amazon VPC, you need to create a\n subnet group before you start creating a cluster. For more information, see Subnets and Subnet Groups.

    \n     " } }, "CacheSecurityGroupNames": { @@ -3721,7 +3721,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Creates a new Amazon ElastiCache cache parameter group. An ElastiCache cache parameter\n group is a collection of parameters and their values that are applied to all of the\n nodes in any cluster or replication group using the CacheParameterGroup.

    \n

    A newly created CacheParameterGroup is an exact duplicate of the default parameter\n group for the CacheParameterGroupFamily. To customize the newly created\n CacheParameterGroup you can change the values of specific parameters. For more\n information, see:

    \n ", + "smithy.api#documentation": "

    Creates a new Amazon ElastiCache cache parameter group. An ElastiCache cache parameter\n group is a collection of parameters and their values that are applied to all of the\n nodes in any cluster or replication group using the CacheParameterGroup.

    \n

    A newly created CacheParameterGroup is an exact duplicate of the default parameter\n group for the CacheParameterGroupFamily. To customize the newly created\n CacheParameterGroup you can change the values of specific parameters. For more\n information, see:

    \n ", "smithy.api#examples": [ { "title": "CreateCacheParameterGroup", @@ -4019,7 +4019,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Global Datastore offers fully managed, fast, reliable and secure\n cross-region replication. Using Global Datastore with Valkey or Redis OSS, you can create cross-region\n read replica clusters for ElastiCache to enable low-latency reads and disaster\n recovery across regions. For more information, see Replication\n Across Regions Using Global Datastore.

    \n " + "smithy.api#documentation": "

    Global Datastore offers fully managed, fast, reliable and secure\n cross-region replication. Using Global Datastore with Valkey or Redis OSS, you can create cross-region\n read replica clusters for ElastiCache to enable low-latency reads and disaster\n recovery across regions. For more information, see Replication\n Across Regions Using Global Datastore.

    \n " } }, "com.amazonaws.elasticache#CreateGlobalReplicationGroupMessage": { @@ -4029,7 +4029,7 @@ "target": "com.amazonaws.elasticache#String", "traits": { "smithy.api#clientOptional": {}, - "smithy.api#documentation": "

    The suffix name of a Global datastore. Amazon ElastiCache automatically applies a\n prefix to the Global datastore ID when it is created. Each Amazon Region has its own\n prefix. For instance, a Global datastore ID created in the US-West-1 region will begin\n with \"dsdfu\" along with the suffix name you provide. The suffix, combined with the\n auto-generated prefix, guarantees uniqueness of the Global datastore name across\n multiple regions.

    \n

    For a full list of Amazon Regions and their respective Global datastore iD prefixes,\n see Using the Amazon CLI with Global datastores .

    ", + "smithy.api#documentation": "

    The suffix name of a Global datastore. Amazon ElastiCache automatically applies a\n prefix to the Global datastore ID when it is created. Each Amazon Region has its own\n prefix. For instance, a Global datastore ID created in the US-West-1 region will begin\n with \"dsdfu\" along with the suffix name you provide. The suffix, combined with the\n auto-generated prefix, guarantees uniqueness of the Global datastore name across\n multiple regions.

    \n

    For a full list of Amazon Regions and their respective Global datastore iD prefixes,\n see Using the Amazon CLI with Global datastores .

    ", "smithy.api#required": {} } }, @@ -4131,7 +4131,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Creates a Valkey or Redis OSS (cluster mode disabled) or a Valkey or Redis OSS (cluster mode enabled) replication\n group.

    \n

    This API can be used to create a standalone regional replication group or a secondary\n replication group associated with a Global datastore.

    \n

    A Valkey or Redis OSS (cluster mode disabled) replication group is a collection of nodes, where\n one of the nodes is a read/write primary and the others are read-only replicas.\n Writes to the primary are asynchronously propagated to the replicas.

    \n

    A Valkey or Redis OSS cluster-mode enabled cluster is comprised of from 1 to 90 shards (API/CLI:\n node groups). Each shard has a primary node and up to 5 read-only replica nodes. The\n configuration can range from 90 shards and 0 replicas to 15 shards and 5 replicas, which\n is the maximum number or replicas allowed.

    \n

    The node or shard limit can be increased to a maximum of 500 per cluster if the Valkey or Redis OSS \n engine version is 5.0.6 or higher. For example, you can choose to configure a 500 node\n cluster that ranges between 83 shards (one primary and 5 replicas per shard) and 500\n shards (single primary and no replicas). Make sure there are enough available IP\n addresses to accommodate the increase. Common pitfalls include the subnets in the subnet\n group have too small a CIDR range or the subnets are shared and heavily used by other\n clusters. For more information, see Creating a Subnet\n Group. For versions below 5.0.6, the limit is 250 per cluster.

    \n

    To request a limit increase, see Amazon Service Limits and\n choose the limit type Nodes per cluster per instance\n type.

    \n

    When a Valkey or Redis OSS (cluster mode disabled) replication group has been successfully created,\n you can add one or more read replicas to it, up to a total of 5 read replicas. If you\n need to increase or decrease the number of node groups (console: shards), you can use scaling. \n For more information, see Scaling self-designed clusters in the ElastiCache User\n Guide.

    \n \n

    This operation is valid for Valkey and Redis OSS only.

    \n     ", + "smithy.api#documentation": "

    Creates a Valkey or Redis OSS (cluster mode disabled) or a Valkey or Redis OSS (cluster mode enabled) replication\n group.

    \n

    This API can be used to create a standalone regional replication group or a secondary\n replication group associated with a Global datastore.

    \n

    A Valkey or Redis OSS (cluster mode disabled) replication group is a collection of nodes, where\n one of the nodes is a read/write primary and the others are read-only replicas.\n Writes to the primary are asynchronously propagated to the replicas.

    \n

    A Valkey or Redis OSS cluster-mode enabled cluster is comprised of from 1 to 90 shards (API/CLI:\n node groups). Each shard has a primary node and up to 5 read-only replica nodes. The\n configuration can range from 90 shards and 0 replicas to 15 shards and 5 replicas, which\n is the maximum number or replicas allowed.

    \n

    The node or shard limit can be increased to a maximum of 500 per cluster if the Valkey or Redis OSS \n engine version is 5.0.6 or higher. For example, you can choose to configure a 500 node\n cluster that ranges between 83 shards (one primary and 5 replicas per shard) and 500\n shards (single primary and no replicas). Make sure there are enough available IP\n addresses to accommodate the increase. Common pitfalls include the subnets in the subnet\n group have too small a CIDR range or the subnets are shared and heavily used by other\n clusters. For more information, see Creating a Subnet\n Group. For versions below 5.0.6, the limit is 250 per cluster.

    \n

    To request a limit increase, see Amazon Service Limits and\n choose the limit type Nodes per cluster per instance\n type.

    \n

    When a Valkey or Redis OSS (cluster mode disabled) replication group has been successfully created,\n you can add one or more read replicas to it, up to a total of 5 read replicas. If you\n need to increase or decrease the number of node groups (console: shards), you can use scaling. \n For more information, see Scaling self-designed clusters in the ElastiCache User\n Guide.

    \n \n

    This operation is valid for Valkey and Redis OSS only.

    \n     ", "smithy.api#examples": [ { "title": "CreateCacheReplicationGroup", @@ -4248,7 +4248,7 @@ "MultiAZEnabled": { "target": "com.amazonaws.elasticache#BooleanOptional", "traits": { - "smithy.api#documentation": "

    A flag indicating if you have Multi-AZ enabled to enhance fault tolerance. For more\n information, see Minimizing Downtime: Multi-AZ.

    " + "smithy.api#documentation": "

    A flag indicating if you have Multi-AZ enabled to enhance fault tolerance. For more\n information, see Minimizing Downtime: Multi-AZ.

    " } }, "NumCacheClusters": { @@ -4284,7 +4284,7 @@ "CacheNodeType": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The compute and memory capacity of the nodes in the node group (shard).

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " + "smithy.api#documentation": "

    The compute and memory capacity of the nodes in the node group (shard).

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " } }, "Engine": { @@ -4296,7 +4296,7 @@ "EngineVersion": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The version number of the cache engine to be used for the clusters in this replication\n group. To view the supported cache engine versions, use the\n DescribeCacheEngineVersions operation.

    \n

    \n Important: You can upgrade to a newer engine version\n (see Selecting\n a Cache Engine and Version) in the ElastiCache User\n Guide, but you cannot downgrade to an earlier engine version. If you want\n to use an earlier engine version, you must delete the existing cluster or replication\n group and create it anew with the earlier engine version.

    " + "smithy.api#documentation": "

    The version number of the cache engine to be used for the clusters in this replication\n group. To view the supported cache engine versions, use the\n DescribeCacheEngineVersions operation.

    \n

    \n Important: You can upgrade to a newer engine version\n (see Selecting\n a Cache Engine and Version) in the ElastiCache User\n Guide, but you cannot downgrade to an earlier engine version. If you want\n to use an earlier engine version, you must delete the existing cluster or replication\n group and create it anew with the earlier engine version.

    " } }, "CacheParameterGroupName": { @@ -4308,7 +4308,7 @@ "CacheSubnetGroupName": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The name of the cache subnet group to be used for the replication group.

    \n \n

    If you're going to launch your cluster in an Amazon VPC, you need to create a\n subnet group before you start creating a cluster. For more information, see Subnets and Subnet Groups.

    \n     " + "smithy.api#documentation": "

    The name of the cache subnet group to be used for the replication group.

    \n \n

    If you're going to launch your cluster in an Amazon VPC, you need to create a\n subnet group before you start creating a cluster. For more information, see Subnets and Subnet Groups.

    \n     " } }, "CacheSecurityGroupNames": { @@ -4416,7 +4416,7 @@ "DataTieringEnabled": { "target": "com.amazonaws.elasticache#BooleanOptional", "traits": { - "smithy.api#documentation": "

    Enables data tiering. Data tiering is only supported for replication groups using the\n r6gd node type. This parameter must be set to true when using r6gd nodes. For more\n information, see Data tiering.

    " + "smithy.api#documentation": "

    Enables data tiering. Data tiering is only supported for replication groups using the\n r6gd node type. This parameter must be set to true when using r6gd nodes. For more\n information, see Data tiering.

    " } }, "NetworkType": { @@ -4949,7 +4949,7 @@ } ], "traits": { - "smithy.api#documentation": "

    For Valkey engine version 7.2 onwards and Redis OSS 6.0 and onwards: Creates a user. For more information, see\n Using Role Based Access Control (RBAC).

    " + "smithy.api#documentation": "

    For Valkey engine version 7.2 onwards and Redis OSS 6.0 and onwards: Creates a user. For more information, see\n Using Role Based Access Control (RBAC).

    " } }, "com.amazonaws.elasticache#CreateUserGroup": { @@ -4987,7 +4987,7 @@ } ], "traits": { - "smithy.api#documentation": "

    For Valkey engine version 7.2 onwards and Redis OSS 6.0 onwards: Creates a user group. For more\n information, see Using Role Based Access Control (RBAC)\n

    " + "smithy.api#documentation": "

    For Valkey engine version 7.2 onwards and Redis OSS 6.0 onwards: Creates a user group. For more\n information, see Using Role Based Access Control (RBAC)\n

    " } }, "com.amazonaws.elasticache#CreateUserGroupMessage": { @@ -6043,7 +6043,7 @@ } ], "traits": { - "smithy.api#documentation": "

    For Valkey engine version 7.2 onwards and Redis OSS 6.0 onwards: Deletes a user. The user will be removed from\n all user groups and in turn removed from all replication groups. For more information,\n see Using Role Based Access Control (RBAC).

    " + "smithy.api#documentation": "

    For Valkey engine version 7.2 onwards and Redis OSS 6.0 onwards: Deletes a user. The user will be removed from\n all user groups and in turn removed from all replication groups. For more information,\n see Using Role Based Access Control (RBAC).

    " } }, "com.amazonaws.elasticache#DeleteUserGroup": { @@ -6069,7 +6069,7 @@ } ], "traits": { - "smithy.api#documentation": "

    For Valkey engine version 7.2 onwards and Redis OSS 6.0 onwards: Deletes a user group. The user group must first\n be disassociated from the replication group before it can be deleted. For more\n information, see Using Role Based Access Control (RBAC).

    " + "smithy.api#documentation": "

    For Valkey engine version 7.2 onwards and Redis OSS 6.0 onwards: Deletes a user group. The user group must first\n be disassociated from the replication group before it can be deleted. For more\n information, see Using Role Based Access Control (RBAC).

    " } }, "com.amazonaws.elasticache#DeleteUserGroupMessage": { @@ -8506,7 +8506,7 @@ "CacheNodeType": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The cache node type filter value. Use this parameter to show only those reservations\n matching the specified cache node type.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " + "smithy.api#documentation": "

    The cache node type filter value. Use this parameter to show only those reservations\n matching the specified cache node type.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " } }, "Duration": { @@ -8887,7 +8887,7 @@ "CacheNodeType": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The cache node type filter value. Use this parameter to show only the available\n offerings matching the specified cache node type.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " + "smithy.api#documentation": "

    The cache node type filter value. Use this parameter to show only the available\n offerings matching the specified cache node type.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " } }, "Duration": { @@ -10482,7 +10482,7 @@ "code": "InsufficientCacheClusterCapacity", "httpResponseCode": 400 }, - "smithy.api#documentation": "

    The requested cache node type is not available in the specified Availability Zone. For\n more information, see InsufficientCacheClusterCapacity in the ElastiCache User Guide.

    ", + "smithy.api#documentation": "

    The requested cache node type is not available in the specified Availability Zone. For\n more information, see InsufficientCacheClusterCapacity in the ElastiCache User Guide.

    ", "smithy.api#error": "client", "smithy.api#httpError": 400 } @@ -10959,7 +10959,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Lists all tags currently on a named resource.

    \n

    A tag is a key-value pair where the key and value are case-sensitive. You can use\n tags to categorize and track all your ElastiCache resources, with the exception of\n global replication group. When you add or remove tags on replication groups, those\n actions will be replicated to all nodes in the replication group. For more information,\n see Resource-level permissions.

    \n

    If the cluster is not in the available state,\n ListTagsForResource returns an error.

    ", + "smithy.api#documentation": "

    Lists all tags currently on a named resource.

    \n

    A tag is a key-value pair where the key and value are case-sensitive. You can use\n tags to categorize and track all your ElastiCache resources, with the exception of\n global replication group. When you add or remove tags on replication groups, those\n actions will be replicated to all nodes in the replication group. For more information,\n see Resource-level permissions.

    \n

    If the cluster is not in the available state,\n ListTagsForResource returns an error.

    ", "smithy.api#examples": [ { "title": "ListTagsForResource", @@ -11284,7 +11284,7 @@ "NewAvailabilityZones": { "target": "com.amazonaws.elasticache#PreferredAvailabilityZoneList", "traits": { - "smithy.api#documentation": "\n

    This option is only supported on Memcached clusters.

    \n     \n

    The list of Availability Zones where the new Memcached cache nodes are created.

    \n

    This parameter is only valid when NumCacheNodes in the request is greater\n than the sum of the number of active cache nodes and the number of cache nodes pending\n creation (which may be zero). The number of Availability Zones supplied in this list\n must match the cache nodes being added in this request.

    \n

    Scenarios:

    \n \n

    The Availability Zone placement of nodes pending creation cannot be modified. If you\n wish to cancel any nodes pending creation, add 0 nodes by setting\n NumCacheNodes to the number of current nodes.

    \n

    If cross-az is specified, existing Memcached nodes remain in their\n current Availability Zone. Only newly created nodes can be located in different\n Availability Zones. For guidance on how to move existing Memcached nodes to different\n Availability Zones, see the Availability Zone\n Considerations section of Cache Node\n Considerations for Memcached.

    \n

    \n Impact of new add/remove requests upon pending requests\n

    \n " + "smithy.api#documentation": "\n

    This option is only supported on Memcached clusters.

    \n     \n

    The list of Availability Zones where the new Memcached cache nodes are created.

    \n

    This parameter is only valid when NumCacheNodes in the request is greater\n than the sum of the number of active cache nodes and the number of cache nodes pending\n creation (which may be zero). The number of Availability Zones supplied in this list\n must match the cache nodes being added in this request.

    \n

    Scenarios:

    \n \n

    The Availability Zone placement of nodes pending creation cannot be modified. If you\n wish to cancel any nodes pending creation, add 0 nodes by setting\n NumCacheNodes to the number of current nodes.

    \n

    If cross-az is specified, existing Memcached nodes remain in their\n current Availability Zone. Only newly created nodes can be located in different\n Availability Zones. For guidance on how to move existing Memcached nodes to different\n Availability Zones, see the Availability Zone\n Considerations section of Cache Node\n Considerations for Memcached.

    \n

    \n Impact of new add/remove requests upon pending requests\n

    \n " } }, "CacheSecurityGroupNames": { @@ -11338,7 +11338,7 @@ "EngineVersion": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The upgraded version of the cache engine to be run on the cache nodes.

    \n

    \n Important: You can upgrade to a newer engine version\n (see Selecting\n a Cache Engine and Version), but you cannot downgrade to an earlier engine\n version. If you want to use an earlier engine version, you must delete the existing\n cluster and create it anew with the earlier engine version.

    " + "smithy.api#documentation": "

    The upgraded version of the cache engine to be run on the cache nodes.

    \n

    \n Important: You can upgrade to a newer engine version\n (see Selecting\n a Cache Engine and Version), but you cannot downgrade to an earlier engine\n version. If you want to use an earlier engine version, you must delete the existing\n cluster and create it anew with the earlier engine version.

    " } }, "AutoMinorVersionUpgrade": { @@ -11374,7 +11374,7 @@ "AuthTokenUpdateStrategy": { "target": "com.amazonaws.elasticache#AuthTokenUpdateStrategyType", "traits": { - "smithy.api#documentation": "

    Specifies the strategy to use to update the AUTH token. This parameter must be\n specified with the auth-token parameter. Possible values:

    \n \n

    For more information, see Authenticating Users with AUTH\n

    " + "smithy.api#documentation": "

    Specifies the strategy to use to update the AUTH token. This parameter must be\n specified with the auth-token parameter. Possible values:

    \n \n

    For more information, see Authenticating Users with AUTH\n

    " } }, "LogDeliveryConfigurations": { @@ -11753,7 +11753,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Modifies the settings for a replication group. This is limited to Valkey and Redis OSS 7 and above.

    \n \n \n

    This operation is valid for Valkey or Redis OSS only.

    \n     ", + "smithy.api#documentation": "

    Modifies the settings for a replication group. This is limited to Valkey and Redis OSS 7 and above.

    \n \n \n

    This operation is valid for Valkey or Redis OSS only.

    \n     ", "smithy.api#examples": [ { "title": "ModifyReplicationGroup", @@ -11921,7 +11921,7 @@ "EngineVersion": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The upgraded version of the cache engine to be run on the clusters in the replication\n group.

    \n

    \n Important: You can upgrade to a newer engine version\n (see Selecting\n a Cache Engine and Version), but you cannot downgrade to an earlier engine\n version. If you want to use an earlier engine version, you must delete the existing\n replication group and create it anew with the earlier engine version.

    " + "smithy.api#documentation": "

    The upgraded version of the cache engine to be run on the clusters in the replication\n group.

    \n

    \n Important: You can upgrade to a newer engine version\n (see Selecting\n a Cache Engine and Version), but you cannot downgrade to an earlier engine\n version. If you want to use an earlier engine version, you must delete the existing\n replication group and create it anew with the earlier engine version.

    " } }, "AutoMinorVersionUpgrade": { @@ -11957,7 +11957,7 @@ "AuthTokenUpdateStrategy": { "target": "com.amazonaws.elasticache#AuthTokenUpdateStrategyType", "traits": { - "smithy.api#documentation": "

    Specifies the strategy to use to update the AUTH token. This parameter must be\n specified with the auth-token parameter. Possible values:

    \n \n

    For more information, see Authenticating Users with AUTH\n

    " + "smithy.api#documentation": "

    Specifies the strategy to use to update the AUTH token. This parameter must be\n specified with the auth-token parameter. Possible values:

    \n \n

    For more information, see Authenticating Users with AUTH\n

    " } }, "UserGroupIdsToAdd": { @@ -12342,6 +12342,12 @@ "traits": { "smithy.api#documentation": "

    The list of user IDs to remove from the user group.

    " } + }, + "Engine": { + "target": "com.amazonaws.elasticache#EngineType", + "traits": { + "smithy.api#documentation": "

    The engine for a user group.

    " + } } }, "traits": { @@ -12388,6 +12394,12 @@ "traits": { "smithy.api#documentation": "

    Specifies how to authenticate the user.

    " } + }, + "Engine": { + "target": "com.amazonaws.elasticache#EngineType", + "traits": { + "smithy.api#documentation": "

    The engine for a specific user.

    " + } } }, "traits": { @@ -13031,7 +13043,7 @@ "ChangeType": { "target": "com.amazonaws.elasticache#ChangeType", "traits": { - "smithy.api#documentation": "

    Indicates whether a change to the parameter is applied immediately or requires a\n reboot for the change to be applied. You can force a reboot or wait until the next\n maintenance window's reboot. For more information, see Rebooting a\n Cluster.

    " + "smithy.api#documentation": "

    Indicates whether a change to the parameter is applied immediately or requires a\n reboot for the change to be applied. You can force a reboot or wait until the next\n maintenance window's reboot. For more information, see Rebooting a\n Cluster.

    " } } }, @@ -13287,7 +13299,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Allows you to purchase a reserved cache node offering. Reserved nodes are not eligible\n for cancellation and are non-refundable. For more information, see Managing Costs with Reserved Nodes.

    ", + "smithy.api#documentation": "

    Allows you to purchase a reserved cache node offering. Reserved nodes are not eligible\n for cancellation and are non-refundable. For more information, see Managing Costs with Reserved Nodes.

    ", "smithy.api#examples": [ { "title": "PurchaseReservedCacheNodesOfferings", @@ -13420,7 +13432,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Reboots some, or all, of the cache nodes within a provisioned cluster. This operation\n applies any modified cache parameter groups to the cluster. The reboot operation takes\n place as soon as possible, and results in a momentary outage to the cluster. During the\n reboot, the cluster status is set to REBOOTING.

    \n

    The reboot causes the contents of the cache (for each cache node being rebooted) to be\n lost.

    \n

    When the reboot is complete, a cluster event is created.

    \n

    Rebooting a cluster is currently supported on Memcached, Valkey and Redis OSS (cluster mode\n disabled) clusters. Rebooting is not supported on Valkey or Redis OSS (cluster mode enabled)\n clusters.

    \n

    If you make changes to parameters that require a Valkey or Redis OSS (cluster mode enabled) cluster\n reboot for the changes to be applied, see Rebooting a Cluster for an alternate process.

    ", + "smithy.api#documentation": "

    Reboots some, or all, of the cache nodes within a provisioned cluster. This operation\n applies any modified cache parameter groups to the cluster. The reboot operation takes\n place as soon as possible, and results in a momentary outage to the cluster. During the\n reboot, the cluster status is set to REBOOTING.

    \n

    The reboot causes the contents of the cache (for each cache node being rebooted) to be\n lost.

    \n

    When the reboot is complete, a cluster event is created.

    \n

    Rebooting a cluster is currently supported on Memcached, Valkey and Redis OSS (cluster mode\n disabled) clusters. Rebooting is not supported on Valkey or Redis OSS (cluster mode enabled)\n clusters.

    \n

    If you make changes to parameters that require a Valkey or Redis OSS (cluster mode enabled) cluster\n reboot for the changes to be applied, see Rebooting a Cluster for an alternate process.

    ", "smithy.api#examples": [ { "title": "RebootCacheCluster", @@ -13631,7 +13643,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Removes the tags identified by the TagKeys list from the named resource.\n A tag is a key-value pair where the key and value are case-sensitive. You can use tags\n to categorize and track all your ElastiCache resources, with the exception of global\n replication group. When you add or remove tags on replication groups, those actions will\n be replicated to all nodes in the replication group. For more information, see Resource-level permissions.

    ", + "smithy.api#documentation": "

    Removes the tags identified by the TagKeys list from the named resource.\n A tag is a key-value pair where the key and value are case-sensitive. You can use tags\n to categorize and track all your ElastiCache resources, with the exception of global\n replication group. When you add or remove tags on replication groups, those actions will\n be replicated to all nodes in the replication group. For more information, see Resource-level permissions.

    ", "smithy.api#examples": [ { "title": "RemoveTagsFromResource", @@ -13762,7 +13774,7 @@ "MultiAZ": { "target": "com.amazonaws.elasticache#MultiAZStatus", "traits": { - "smithy.api#documentation": "

    A flag indicating if you have Multi-AZ enabled to enhance fault tolerance. For more\n information, see Minimizing Downtime: Multi-AZ\n

    " + "smithy.api#documentation": "

    A flag indicating if you have Multi-AZ enabled to enhance fault tolerance. For more\n information, see Minimizing Downtime: Multi-AZ\n

    " } }, "ConfigurationEndpoint": { @@ -13858,7 +13870,7 @@ "DataTiering": { "target": "com.amazonaws.elasticache#DataTieringStatus", "traits": { - "smithy.api#documentation": "

    Enables data tiering. Data tiering is only supported for replication groups using the\n r6gd node type. This parameter must be set to true when using r6gd nodes. For more\n information, see Data tiering.

    " + "smithy.api#documentation": "

    Enables data tiering. Data tiering is only supported for replication groups using the\n r6gd node type. This parameter must be set to true when using r6gd nodes. For more\n information, see Data tiering.

    " } }, "AutoMinorVersionUpgrade": { @@ -14101,7 +14113,7 @@ "CacheNodeType": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The cache node type for the reserved cache nodes.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " + "smithy.api#documentation": "

    The cache node type for the reserved cache nodes.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " } }, "StartTime": { @@ -14262,7 +14274,7 @@ "CacheNodeType": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The cache node type for the reserved cache node.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " + "smithy.api#documentation": "

    The cache node type for the reserved cache node.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " } }, "Duration": { @@ -14942,7 +14954,7 @@ "ServiceUpdateRecommendedApplyByDate": { "target": "com.amazonaws.elasticache#TStamp", "traits": { - "smithy.api#documentation": "

    The recommendend date to apply the service update in order to ensure compliance. For\n information on compliance, see Self-Service Security Updates for Compliance.

    " + "smithy.api#documentation": "

    The recommendend date to apply the service update in order to ensure compliance. For\n information on compliance, see Self-Service Security Updates for Compliance.

    " } }, "ServiceUpdateStatus": { @@ -15192,7 +15204,7 @@ "CacheNodeType": { "target": "com.amazonaws.elasticache#String", "traits": { - "smithy.api#documentation": "

    The name of the compute and memory capacity node type for the source cluster.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " + "smithy.api#documentation": "

    The name of the compute and memory capacity node type for the source cluster.

    \n

    The following node types are supported by ElastiCache. Generally speaking, the current\n generation types provide more memory and computational power at lower cost when compared\n to their equivalent previous generation counterparts.

    \n \n

    \n Additional node type info\n

    \n " } }, "Engine": { @@ -15318,7 +15330,7 @@ "DataTiering": { "target": "com.amazonaws.elasticache#DataTieringStatus", "traits": { - "smithy.api#documentation": "

    Enables data tiering. Data tiering is only supported for replication groups using the\n r6gd node type. This parameter must be set to true when using r6gd nodes. For more\n information, see Data tiering.

    " + "smithy.api#documentation": "

    Enables data tiering. Data tiering is only supported for replication groups using the\n r6gd node type. This parameter must be set to true when using r6gd nodes. For more\n information, see Data tiering.

    " } } }, @@ -15760,7 +15772,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Represents the input of a TestFailover operation which tests automatic\n failover on a specified node group (called shard in the console) in a replication group\n (called cluster in the console).

    \n

    This API is designed for testing the behavior of your application in case of\n ElastiCache failover. It is not designed to be an operational tool for initiating a\n failover to overcome a problem you may have with the cluster. Moreover, in certain\n conditions such as large-scale operational events, Amazon may block this API.

    \n

    \n Note the following\n

    \n \n

    Also see, Testing\n Multi-AZ in the ElastiCache User Guide.

    " + "smithy.api#documentation": "

    Represents the input of a TestFailover operation which tests automatic\n failover on a specified node group (called shard in the console) in a replication group\n (called cluster in the console).

    \n

    This API is designed for testing the behavior of your application in case of\n ElastiCache failover. It is not designed to be an operational tool for initiating a\n failover to overcome a problem you may have with the cluster. Moreover, in certain\n conditions such as large-scale operational events, Amazon may block this API.

    \n

    \n Note the following\n

    \n \n

    Also see, Testing\n Multi-AZ in the ElastiCache User Guide.

    " } }, "com.amazonaws.elasticache#TestFailoverMessage": { @@ -16014,7 +16026,7 @@ "ServiceUpdateRecommendedApplyByDate": { "target": "com.amazonaws.elasticache#TStamp", "traits": { - "smithy.api#documentation": "

    The recommended date to apply the service update to ensure compliance. For information\n on compliance, see Self-Service Security Updates for Compliance.

    " + "smithy.api#documentation": "

    The recommended date to apply the service update to ensure compliance. For information\n on compliance, see Self-Service Security Updates for Compliance.

    " } }, "ServiceUpdateType": {