- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Okay - this is weird! In my scenario, there was some difference between the table and my stack. I /think/ it comes down to having this:
SSESpecification:
KMSMasterKeyId: !Ref ConnectionsTableKey
SSEEnabled: true
SSEType: KMS
In this case, the SSEType
line is confusing things, as I want to use customer-managed keys, not the AWS default KMS for Dynamo. Removing this line, adding quotes around PAY_PER_REQUEST
and a couple other small changes (removing the DeletionPolicy
and UpdateReplacePolicy
) seem to have fixed the issue.
Hello,
Couldn't get your exact issue. The below code block is working good for me and creating the table as well as GSI. both are ondemand capacity units.
Please let me if you still have any issues
PS : I have removed the KMS key reference, you can add it back and test.
AWSTemplateFormatVersion: "2010-09-09"
Resources:
ConnectionsTable:
Type: AWS::DynamoDB::Table
DeletionPolicy: Delete
UpdateReplacePolicy: Delete
Properties:
AttributeDefinitions:
- AttributeName: UserID
AttributeType: 'S'
- AttributeName: WebsocketID
AttributeType: 'S'
KeySchema:
- AttributeName: UserID
KeyType: HASH
GlobalSecondaryIndexes:
- IndexName: "WebsocketID"
KeySchema:
- AttributeName: WebsocketID
KeyType: HASH
Projection:
NonKeyAttributes:
- AgentID
ProjectionType: "INCLUDE"
ProvisionedThroughput:
ReadCapacityUnits: "0"
WriteCapacityUnits: "0"
BillingMode: PAY_PER_REQUEST
PointInTimeRecoverySpecification:
PointInTimeRecoveryEnabled: false
TimeToLiveSpecification:
AttributeName: ExpiryTimestamp
Enabled: true
Hi,
That's right. When you want to use Customer Managed Key (CMK) by specifying "KMSMasterKeyId" , Then you dont have to mention SSEEnabled and SSEType.
These 2 options applicable only when you want to use default aws managed key.
Contenuto pertinente
- AWS UFFICIALEAggiornata 7 mesi fa
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata 9 mesi fa