diff --git a/codegen/sdk-codegen/aws-models/dynamodb.json b/codegen/sdk-codegen/aws-models/dynamodb.json
index 803f6d0f4bb..b9f38b80d5d 100644
--- a/codegen/sdk-codegen/aws-models/dynamodb.json
+++ b/codegen/sdk-codegen/aws-models/dynamodb.json
@@ -3732,6 +3732,9 @@
},
"aws.protocols#awsJson1_0": {},
"smithy.api#documentation": "
Amazon DynamoDB is a fully managed NoSQL database service that provides fast\n and predictable performance with seamless scalability. DynamoDB lets you\n offload the administrative burdens of operating and scaling a distributed database, so\n that you don't have to worry about hardware provisioning, setup and configuration,\n replication, software patching, or cluster scaling.
\nWith DynamoDB, you can create database tables that can store and retrieve\n any amount of data, and serve any level of request traffic. You can scale up or scale\n down your tables' throughput capacity without downtime or performance degradation, and\n use the Amazon Web Services Management Console to monitor resource utilization and performance\n metrics.
\nDynamoDB automatically spreads the data and traffic for your tables over\n a sufficient number of servers to handle your throughput and storage requirements, while\n maintaining consistent and fast performance. All of your data is stored on solid state\n disks (SSDs) and automatically replicated across multiple Availability Zones in an\n Amazon Web Services Region, providing built-in high availability and data\n durability.
", + "smithy.api#suppress": [ + "RuleSetAwsBuiltIn.AWS::Auth::AccountId" + ], "smithy.api#title": "Amazon DynamoDB", "smithy.api#xmlNamespace": { "uri": "http://dynamodb.amazonaws.com/doc/2012-08-10/" @@ -11975,7 +11978,7 @@ "aws.api#clientDiscoveredEndpoint": { "required": false }, - "smithy.api#documentation": "Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB\n Streams settings for a given table.
\nThis operation only applies to Version 2019.11.21 (Current) \n of global tables.\n
\nYou can only perform one of the following operations at once:
\nModify the provisioned throughput settings of the table.
\nRemove a global secondary index from the table.
\nCreate a new global secondary index on the table. After the index begins\n backfilling, you can use UpdateTable
to perform other\n operations.
\n UpdateTable
is an asynchronous operation; while it is executing, the table\n status changes from ACTIVE
to UPDATING
. While it is\n UPDATING
, you cannot issue another UpdateTable
request.\n When the table returns to the ACTIVE
state, the UpdateTable
\n operation is complete.
Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB\n Streams settings for a given table.
\nThis operation only applies to Version 2019.11.21 (Current) \n of global tables.\n
\nYou can only perform one of the following operations at once:
\nModify the provisioned throughput settings of the table.
\nRemove a global secondary index from the table.
\nCreate a new global secondary index on the table. After the index begins\n backfilling, you can use UpdateTable
to perform other\n operations.
\n UpdateTable
is an asynchronous operation; while\n it's\n executing, the table status changes from ACTIVE
to UPDATING
.\n While it's UPDATING
, you can't issue another UpdateTable
\n request on the\n base table nor any replicas. When the table returns to the\n ACTIVE
state, the UpdateTable
operation is\n complete.
(Kinesis and DynamoDB Streams only) An Amazon SQS queue or Amazon SNS topic destination for discarded records.
" + "smithy.api#documentation": "(Kinesis, DynamoDB Streams, Amazon MSK, and self-managed Apache Kafka event sources only) A configuration object that specifies the destination of an event after Lambda processes it.
" } }, "Topics": { @@ -8667,7 +8667,7 @@ "Destination": { "target": "com.amazonaws.lambda#DestinationArn", "traits": { - "smithy.api#documentation": "The Amazon Resource Name (ARN) of the destination resource.
\nTo retain records of asynchronous invocations,\n you can configure an Amazon SNS topic, Amazon SQS queue, Lambda function,\n or Amazon EventBridge event bus as the destination.
\nTo retain records of failed invocations from Kinesis and\n DynamoDB event sources, you can configure an Amazon SNS topic or\n Amazon SQS queue as the destination.
\nTo retain records of failed invocations from self-managed Kafka or\n Amazon MSK,\n you can configure an Amazon SNS topic or Amazon SQS queue as the destination.
" + "smithy.api#documentation": "The Amazon Resource Name (ARN) of the destination resource.
\nTo retain records of asynchronous invocations,\n you can configure an Amazon SNS topic, Amazon SQS queue, Lambda function,\n or Amazon EventBridge event bus as the destination.
\nTo retain records of failed invocations from Kinesis and\n DynamoDB event sources, you can configure an Amazon SNS topic or\n Amazon SQS queue as the destination.
\nTo retain records of failed invocations from self-managed Kafka or\n Amazon MSK,\n you can configure an Amazon SNS topic, Amazon SQS queue, or Amazon S3 bucket as the destination.
" } } }, @@ -9999,6 +9999,12 @@ "smithy.api#enumValue": "dotnet6" } }, + "dotnet8": { + "target": "smithy.api#Unit", + "traits": { + "smithy.api#enumValue": "dotnet8" + } + }, "nodejs43edge": { "target": "smithy.api#Unit", "traits": {