Skip to content

giuseppe-trisciuoglio/developer-kit / plugins/developer-kit-aws/skills/aws-cloudformation/aws-cloudformation-dynamodb

aws-cloudformation-dynamodb

Verified

Provides AWS CloudFormation patterns for DynamoDB tables, GSIs, LSIs, auto-scaling, and streams. Use when creating DynamoDB tables with CloudFormation, configuring primary keys, local/global secondary indexes, capacity modes (on-demand/provisioned), point-in-time recovery, encryption, TTL, and implementing template structure with Parameters, Outputs, Mappings, Conditions, cross-stack references.

AWS CloudFormation DynamoDB Patterns

Provides production-ready NoSQL database infrastructure patterns using AWS CloudFormation templates with DynamoDB tables, GSIs, LSIs, auto-scaling, encryption, TTL, and streams.

Overview

Covers DynamoDB tables, primary keys, secondary indexes (GSI/LSI), capacity modes, auto-scaling, encryption, TTL, streams, and best practices for parameters, outputs, and cross-stack references.

When to Use

Creating DynamoDB tables, configuring keys and indexes, setting capacity modes, implementing auto-scaling, enabling encryption/TTL/streams, and organizing CloudFormation templates.

Instructions

Follow these steps to create DynamoDB tables with CloudFormation:

  1. Define Table Parameters: Specify table name and billing mode
  2. Configure Primary Key: Set partition key and optional sort key
  3. Add Secondary Indexes: Create GSIs for alternative access patterns
  4. Configure Encryption: Enable encryption using KMS keys
  5. Set Up TTL: Define timestamp attribute for automatic deletion
  6. Enable Streams: Configure stream for change data capture
  7. Add Auto Scaling: Implement Application Auto Scaling for provisioned capacity
  8. Create Backup: Enable point-in-time recovery
  9. Validate Template: Run aws cloudformation validate-template before deployment
  10. Deploy Stack: Use aws cloudformation create-stack or update-stack
  11. Monitor Events: Check aws cloudformation describe-stack-events for failures or ROLLBACK status
  12. Handle Rollback: On failure, review events for resource errors, fix the template, and re-deploy

Quick Reference

Resource TypePurpose
AWS::DynamoDB::TableCreate DynamoDB table
AWS::ApplicationAutoScaling::ScalableTargetAuto scaling configuration
AWS::ApplicationAutoScaling::ScalingPolicyScaling policies
AWS::KMS::KeyKMS key for encryption
AWS::IAM::RoleIAM roles for auto scaling
BillingModePAY_PER_REQUEST or PROVISIONED
SSESpecificationServer-side encryption

Examples

Basic Table with On-Demand Capacity

DynamoDBTable:
  Type: AWS::DynamoDB::Table
  Properties:
    TableName: !Sub "${AWS::StackName}-table"
    BillingMode: PAY_PER_REQUEST
    AttributeDefinitions:
      - AttributeName: pk
        AttributeType: S
    KeySchema:
      - AttributeName: pk
        KeyType: HASH

Table with Global Secondary Index

DynamoDBTable:
  Type: AWS::DynamoDB::Table
  Properties:
    TableName: !Sub "${AWS::StackName}-table"
    BillingMode: PAY_PER_REQUEST
    AttributeDefinitions:
      - AttributeName: pk
        AttributeType: S
      - AttributeName: gsi-pk
        AttributeType: S
    KeySchema:
      - AttributeName: pk
        KeyType: HASH
    GlobalSecondaryIndexes:
      - IndexName: gsi-index
        KeySchema:
          - AttributeName: gsi-pk
            KeyType: HASH
        Projection:
          ProjectionType: ALL

Table with TTL

SessionTable:
  Type: AWS::DynamoDB::Table
  Properties:
    TableName: !Sub "${AWS::StackName}-sessions"
    BillingMode: PAY_PER_REQUEST
    AttributeDefinitions:
      - AttributeName: sessionId
        AttributeType: S
    KeySchema:
      - AttributeName: sessionId
        KeyType: HASH
    TimeToLiveSpecification:
      AttributeName: expiresAt
      Enabled: true

Table with Auto Scaling

ScalableTarget:
  Type: AWS::ApplicationAutoScaling::ScalableTarget
  Properties:
    MaxCapacity: 100
    MinCapacity: 5
    ResourceId: !Sub "table/${DynamoDBTable}"
    RoleARN: !GetAtt AutoScalingRole.Arn
    ScalableDimension: dynamodb:table:ReadCapacityUnits
    ServiceNamespace: dynamodb

See references/complete-examples.md for more complete examples including encryption, streams, auto scaling, and production tables.

Template Structure

Base Template

AWSTemplateFormatVersion: 2010-09-09
Description: DynamoDB table with GSI and auto-scaling

Parameters:
  TableName:
    Type: String
    Default: my-table
  BillingMode:
    Type: String
    Default: PAY_PER_REQUEST

Resources:
  DynamoDBTable:
    Type: AWS::DynamoDB::Table
    Properties:
      TableName: !Ref TableName
      BillingMode: !Ref BillingMode

Outputs:
  TableName:
    Value: !Ref DynamoDBTable
  TableArn:
    Value: !GetAtt DynamoDBTable.Arn

See references/advanced-configuration.md for detailed Parameters, Mappings, Conditions, Outputs, IAM roles, and cross-stack references.

Best Practices

  1. Use PAY_PER_REQUEST for development/testing and unpredictable workloads
  2. Enable Point-In-Time Recovery for production tables
  3. Use KMS encryption for sensitive data (SSE-KMS)
  4. Configure auto-scaling for provisioned capacity tables
  5. Design GSIs carefully - each GSI consumes capacity
  6. Use TTL for automatic data expiration (sessions, cache)
  7. Enable Streams for change data capture and analytics
  8. Tag resources for cost allocation and organization
  9. Export outputs for cross-stack references
  10. Use Conditions for environment-specific configurations

Common Troubleshooting

Table already exists: Use unique table names or stack deletion policy GSI creation fails: Verify attribute definitions include GSI attributes Auto-scaling not working: Check IAM role permissions and service-linked role TTL not expiring: Ensure TTL attribute is Number type, not String Streams not enabled: Can only enable streams during table creation Encryption errors: Verify KMS key exists in same region as table

Related Skills

References

Complete Examples

Advanced Configuration

Constraints and Warnings

  • Table names: Must be unique per region (globally unique for global tables)
  • GSI limits: Maximum 5 GSIs per table (for single-region tables)
  • LSI limits: Maximum 5 LSIs per table, same partition key as table
  • Capacity limits: On-demand has default account limits (40,000 RCUs, 40,000 WCUs)
  • Auto-scaling: Requires PROVISIONED billing mode (not PAY_PER_REQUEST)
  • Point-in-time recovery: Can only be enabled during table creation
  • Streams: Can only be enabled during table creation
  • Encryption: KMS keys must be in same region as table
  • TTL: Attribute must be Number type, measured in seconds
  • Throughput: Each GSI shares provisioned throughput with table
  • Item size limit: Maximum 400 KB per item
  • Hot partition: Design keys to avoid hot partition issues
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexVerifiedInstall