chore(dynamodb): changing language for multi-attribute keys on GSI's (#36233)

### Issue # (if applicable)

No issue raised

### Reason for this change

Language around multi-attribute keys for global secondary indexes needed updating.

### Description of changes

Descriptions of attributes changed, no code changes.

### Describe any new or updated permissions being added




### Description of how you validated changes



### Checklist
- [X] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

Author: LeeroyHannigan

packages/aws-cdk-lib/aws-dynamodb/README.md

@@ -404,9 +404,9 @@ const table = new dynamodb.TableV2(this, 'Table', {
 });
 ```
 
-#### Compound Keys
+#### Multi-attribute Keys
 
-Global secondary indexes support compound keys, allowing you to specify multiple partition keys and/or multiple sort keys. This enables more flexible query patterns for complex data models.
+Global secondary indexes support multi-attribute keys, allowing you to specify multiple partition keys and/or multiple sort keys. This enables more flexible query patterns for complex data models.
 
 **Key Constraints:**
 - You can specify up to **4 partition keys** per global secondary index
@@ -417,14 +417,14 @@ Global secondary indexes support compound keys, allowing you to specify multiple
 - For multiple keys, you **must** use the plural parameters (`partitionKeys` and/or `sortKeys`)
 - **Keys cannot be added or modified after index creation** - attempting to add additional keys to an existing index will result in an error
 
-**Example with compound partition and sort keys:**
+**Example with multi-attribute partition and sort keys:**
 
 ```ts
 const table = new dynamodb.TableV2(this, 'Table', {
   partitionKey: { name: 'pk', type: dynamodb.AttributeType.STRING },
   globalSecondaryIndexes: [
     {
-      indexName: 'compound-gsi',
+      indexName: 'multi-attribute-gsi',
       partitionKeys: [
         { name: 'gsi_pk1', type: dynamodb.AttributeType.STRING },
         { name: 'gsi_pk2', type: dynamodb.AttributeType.NUMBER },
@@ -456,12 +456,12 @@ table.addGlobalSecondaryIndex({
   partitionKey: { name: 'pk', type: dynamodb.AttributeType.STRING },
 });
 
-// Add a GSI with compound keys
+// Add a GSI with multi-attribute keys
 table.addGlobalSecondaryIndex({
-  indexName: 'compound-gsi2',
+  indexName: 'multi-attribute-gsi2',
   partitionKeys: [
-    { name: 'compound_pk1', type: dynamodb.AttributeType.STRING },
-    { name: 'compound_pk2', type: dynamodb.AttributeType.NUMBER },
+    { name: 'multi-attribute_pk1', type: dynamodb.AttributeType.STRING },
+    { name: 'multi-attribute_pk2', type: dynamodb.AttributeType.NUMBER },
   ],
   sortKey: { name: 'sk', type: dynamodb.AttributeType.STRING },
 });

packages/aws-cdk-lib/aws-dynamodb/TABLE_V1_API.md

@@ -211,12 +211,12 @@ To get the partition key and sort key of the table or indexes you have configure
 ```ts
 declare const table: dynamodb.Table;
 
-// For single keys, use schema() (deprecated for compound keys)
+// For single keys, use schema() (deprecated for multi-attribute keys)
 const schema = table.schema();
 const partitionKey = schema.partitionKey;
 const sortKey = schema.sortKey;
 
-// For compound keys, use schemaV2() which returns normalized arrays
+// For multi-attribute keys, use schemaV2() which returns normalized arrays
 const schemaV2 = table.schemaV2();
 const partitionKeys = schemaV2.partitionKeys; // Attribute[]
 const sortKeys = schemaV2.sortKeys; // Attribute[]
@@ -225,11 +225,11 @@ const sortKeys = schemaV2.sortKeys; // Attribute[]
 const indexSchema = table.schemaV2('INDEX_NAME');
 ```
 
-Note: `schema()` is deprecated for indexes with compound keys and will throw an error. Use `schemaV2()` instead, which always returns normalized arrays.
+Note: `schema()` is deprecated for indexes with multi-attribute keys and will throw an error. Use `schemaV2()` instead, which always returns normalized arrays.
 
-## Global Secondary Indexes with Compound Keys
+## Global Secondary Indexes with multi-attribute Keys
 
-Global secondary indexes support compound keys, allowing you to specify multiple partition keys and/or multiple sort keys. This enables more flexible query patterns for complex data models.
+Global secondary indexes support multi-attribute keys, allowing you to specify multiple partition keys and/or multiple sort keys. This enables more flexible query patterns for complex data models.
 
 **Key Constraints:**
 - You can specify up to **4 partition keys** per global secondary index
@@ -249,7 +249,7 @@ const table = new dynamodb.Table(this, 'Table', {
 });
 
 table.addGlobalSecondaryIndex({
-  indexName: 'compound-gsi',
+  indexName: 'multi-attribute-gsi',
   partitionKeys: [
     { name: 'gsi_pk1', type: dynamodb.AttributeType.STRING },
     { name: 'gsi_pk2', type: dynamodb.AttributeType.NUMBER },

packages/aws-cdk-lib/aws-dynamodb/lib/shared.ts

@@ -565,15 +565,15 @@ export interface KeySchema {
 }
 
 /**
- * A key schema that combines the legacy properties (singular keys) with the modern properties (compound keys)
+ * A key schema that combines the legacy properties (singular keys) with the modern properties (multi-attribute keys)
  *
  * Picking from an existing type is an easy way to get these without having to copy/paste them all, but we could
  * have also done the copy/pasting. This type is never exported.
  */
 type CompatibleKeySchema = Pick<GlobalSecondaryIndexProps, 'partitionKey' | 'partitionKeys' | 'sortKey' | 'sortKeys'>;
 
 /**
- * Parse a backwards compatible key schema to a strictly compound key schema, and validate the contents
+ * Parse a backwards compatible key schema to a strictly multi-attribute key schema, and validate the contents
  */
 export function parseKeySchema(schema: CompatibleKeySchema, scope: IConstruct): KeySchema {
   if ((schema.partitionKey === undefined) === (schema.partitionKeys === undefined)) {

packages/aws-cdk-lib/aws-dynamodb/lib/table-v2.ts

@@ -94,7 +94,7 @@ export interface GlobalSecondaryIndexPropsV2 extends SecondaryIndexProps {
    * Partition key attribute definition.
    *
    * If a single field forms the partition key, you can use this field.  Use the
-   * `partitionKeys` field if the partition key is a compound key (consists of
+   * `partitionKeys` field if the partition key is a multi-attribute key (consists of
    * multiple fields).
    *
    * @default - exactly one of `partitionKey` and `partitionKeys` must be specified.
@@ -105,21 +105,21 @@ export interface GlobalSecondaryIndexPropsV2 extends SecondaryIndexProps {
    * Sort key attribute definition.
    *
    * If a single field forms the sort key, you can use this field.  Use the
-   * `sortKeys` field if the sort key is a compound key (consists of multiple
+   * `sortKeys` field if the sort key is a multi-attribute key (consists of multiple
    * fields).
    *
    * @default - no sort key
    */
   readonly sortKey?: Attribute;
 
   /**
-   * Compound partition key
+   * Multi-attribute partition key
    *
    * If a single field forms the partition key, you can use either
    * `partitionKey` or `partitionKeys` to specify the partition key. Exactly
    * one of these must be specified.
    *
-   * You must use `partitionKeys` field if the partition key is a compound key
+   * You must use `partitionKeys` field if the partition key is a multi-attribute key
    * (consists of multiple fields).
    *
    * NOTE: although the name of this field makes it sound like it creates
@@ -133,13 +133,13 @@ export interface GlobalSecondaryIndexPropsV2 extends SecondaryIndexProps {
   readonly partitionKeys?: Attribute[];
 
   /**
-   * Compound sort key
+   * Multi-attribute sort key
    *
    * If a single field forms the sort key, you can use either
    * `sortKey` or `sortKeys` to specify the sort key. At most one of these
    * may be specified.
    *
-   * You must use `sortKeys` field if the sort key is a compound key
+   * You must use `sortKeys` field if the sort key is a multi-attribute key
    * (consists of multiple fields).
    *
    * NOTE: although the name of this field makes it sound like it creates

packages/aws-cdk-lib/aws-dynamodb/lib/table.ts

@@ -48,7 +48,7 @@ export interface SchemaOptions {
    * Partition key attribute definition.
    *
    * If a single field forms the partition key, you can use this field.  Use the
-   * `partitionKeys` field if the partition key is a compound key (consists of
+   * `partitionKeys` field if the partition key is a multi-attribute key (consists of
    * multiple fields).
    *
    * @default - exactly one of `partitionKey` and `partitionKeys` must be specified.
@@ -59,7 +59,7 @@ export interface SchemaOptions {
    * Sort key attribute definition.
    *
    * If a single field forms the sort key, you can use this field.  Use the
-   * `sortKeys` field if the sort key is a compound key (consists of multiple
+   * `sortKeys` field if the sort key is a multi-attribute key (consists of multiple
    * fields).
    *
    * @default - no sort key
@@ -515,13 +515,13 @@ export interface TableProps extends TableOptions {
  */
 export interface GlobalSecondaryIndexProps extends SecondaryIndexProps, SchemaOptions {
   /**
-   * Compound partition key
+   * Multi-attribute partition key
    *
    * If a single field forms the partition key, you can use either
    * `partitionKey` or `partitionKeys` to specify the partition key. Exactly
    * one of these must be specified.
    *
-   * You must use `partitionKeys` field if the partition key is a compound key
+   * You must use `partitionKeys` field if the partition key is a multi-attribute key
    * (consists of multiple fields).
    *
    * NOTE: although the name of this field makes it sound like it creates
@@ -535,13 +535,13 @@ export interface GlobalSecondaryIndexProps extends SecondaryIndexProps, SchemaOp
   readonly partitionKeys?: Attribute[];
 
   /**
-   * Compound sort key
+   * Multi-attribute sort key
    *
    * If a single field forms the sort key, you can use either
    * `sortKey` or `sortKeys` to specify the sort key. At most one of these
    * may be specified.
    *
-   * You must use `sortKeys` field if the sort key is a compound key
+   * You must use `sortKeys` field if the sort key is a multi-attribute key
    * (consists of multiple fields).
    *
    * NOTE: although the name of this field makes it sound like it creates
@@ -1580,7 +1580,7 @@ export class Table extends TableBase {
     }
 
     if (schema.partitionKeys.length > 1 || schema.sortKeys.length > 1) {
-      throw new ValidationError(`Index ${indexName} uses compound keys and cannot be returned by schema(), use schemaV2() instead.`, this);
+      throw new ValidationError(`Index ${indexName} uses multi-attribute keys and cannot be returned by schema(), use schemaV2() instead.`, this);
     }
 
     return {

packages/aws-cdk-lib/aws-dynamodb/test/dynamodb.test.ts

@@ -1358,7 +1358,7 @@ describe('schema details', () => {
       });
     });
 
-    test('get normalized schema for GSI with compound partition keys', () => {
+    test('get normalized schema for GSI with multi-attribute partition keys', () => {
       const pk1: Attribute = { name: 'pk1', type: AttributeType.STRING };
       const pk2: Attribute = { name: 'pk2', type: AttributeType.STRING };
 
@@ -1373,7 +1373,7 @@ describe('schema details', () => {
       });
     });
 
-    test('get normalized schema for GSI with compound sort keys', () => {
+    test('get normalized schema for GSI with multi-attribute sort keys', () => {
       const sk1: Attribute = { name: 'sk1', type: AttributeType.STRING };
       const sk2: Attribute = { name: 'sk2', type: AttributeType.STRING };
 
@@ -4879,7 +4879,7 @@ test('ContributorInsightsSpecification && ContributorInsightsEnabled', () => {
   }).toThrow('`contributorInsightsSpecification` and `contributorInsightsEnabled` are set. Use `contributorInsightsSpecification` only.');
 });
 
-test('Compound partition keys for global secondary index', () => {
+test('Multi-attribute partition keys for global secondary index', () => {
   const stack = new Stack();
 
   const table = new Table(stack, CONSTRUCT_NAME, {
@@ -4918,7 +4918,7 @@ test('Compound partition keys for global secondary index', () => {
   );
 });
 
-test('Compound partition keys and standard sort key for global secondary index', () => {
+test('Multi-attribute partition keys and standard sort key for global secondary index', () => {
   const stack = new Stack();
 
   const table = new Table(stack, CONSTRUCT_NAME, {
@@ -4960,7 +4960,7 @@ test('Compound partition keys and standard sort key for global secondary index',
   );
 });
 
-test('Throws when compound partitionKeys and partitionKey are specified', () => {
+test('Throws when multi-attribute partitionKeys and partitionKey are specified', () => {
   const stack = new Stack();
   expect(() => {
     const table = new Table(stack, CONSTRUCT_NAME, {
@@ -4977,7 +4977,7 @@ test('Throws when compound partitionKeys and partitionKey are specified', () =>
   }).toThrow('Exactly one of \'partitionKey\', \'partitionKeys\' must be specified');
 });
 
-test('Throws when compound sortKeys and sortKey are specified', () => {
+test('Throws when multi-attribute sortKeys and sortKey are specified', () => {
   const stack = new Stack();
   expect(() => {
     const table = new Table(stack, CONSTRUCT_NAME, {
@@ -4994,7 +4994,7 @@ test('Throws when compound sortKeys and sortKey are specified', () => {
   }).toThrow('At most one of \'sortKey\', \'sortKeys\' may be specified');
 });
 
-test('Throws when more than four compound partition keys are specified', () => {
+test('Throws when more than four multi-attribute partition keys are specified', () => {
   const stack = new Stack();
   expect(() => {
     const table = new Table(stack, CONSTRUCT_NAME, {
@@ -5013,7 +5013,7 @@ test('Throws when more than four compound partition keys are specified', () => {
   }).toThrow('Maximum of 4 partition keys allowed');
 });
 
-test('Throws when more than four compound sort keys are specified', () => {
+test('Throws when more than four multi-attribute sort keys are specified', () => {
   const stack = new Stack();
   expect(() => {
     const table = new Table(stack, CONSTRUCT_NAME, {

packages/aws-cdk-lib/aws-dynamodb/test/table-v2.test.ts

@@ -3716,7 +3716,7 @@ test('ContributorInsightsSpecification && ContributorInsights - v2', () => {
   }).toThrow('`contributorInsightsSpecification` and `contributorInsights` are set. Use `contributorInsightsSpecification` only.');
 });
 
-test('can add GSI with compound partition keys', () => {
+test('can add GSI with multi-attribute partition keys', () => {
   const stack = new Stack();
   const table = new TableV2(stack, 'Table', {
     partitionKey: { name: 'pk', type: AttributeType.STRING },
@@ -3748,7 +3748,7 @@ test('can add GSI with compound partition keys', () => {
   });
 });
 
-test('can add GSI with compound sort keys', () => {
+test('can add GSI with multi-attribute sort keys', () => {
   const stack = new Stack();
   const table = new TableV2(stack, 'Table', {
     partitionKey: { name: 'pk', type: AttributeType.STRING },
@@ -3862,7 +3862,7 @@ test('throws when no partition key specified', () => {
   }).toThrow('Exactly one of \'partitionKey\', \'partitionKeys\' must be specified');
 });
 
-test('can add GSI with both compound partition and sort keys', () => {
+test('can add GSI with both multi-attribute partition and sort keys', () => {
   const stack = new Stack();
   const table = new TableV2(stack, 'Table', {
     partitionKey: { name: 'pk', type: AttributeType.STRING },