Skip to main content
MEDIUMDynamoDBSecurity

DynamoDB Table Uses AWS-Owned Encryption Key

dynamodb-encryption-aws-owned-key

What this rule checks

Detects AWS::DynamoDB::Table resources without SSESpecification.SSEEnabled=true. DynamoDB always encrypts at rest, but the default AWS-owned key cannot be inspected, audited, or rotated by the customer โ€” inadequate for HIPAA / PCI-DSS / FedRAMP workloads.

How to fix it

  1. 1Set SSESpecification.SSEEnabled to true on the table
  2. 2Provide SSESpecification.KMSMasterKeyId pointing at a customer-managed KMS key
  3. 3Verify the KMS key has rotation enabled (kms-key-rotation-disabled covers this)
FlaggedWith no SSESpecification, the table falls back to the AWS-owned key, which you cannot inspect, audit, or rotate.
import { Stack, App } from 'aws-cdk-lib';
import { Construct } from 'constructs';
import * as dynamodb from 'aws-cdk-lib/aws-dynamodb';

new dynamodb.Table(this, 'Table', {
  partitionKey: { name: 'id', type: dynamodb.AttributeType.STRING },
});
FixedA customer-managed KMS key sets SSESpecification.SSEEnabled with an auditable, rotatable KMSMasterKeyId.
import { Stack, App } from 'aws-cdk-lib';
import { Construct } from 'constructs';
import * as dynamodb from 'aws-cdk-lib/aws-dynamodb';
import * as kms from 'aws-cdk-lib/aws-kms';

new dynamodb.Table(this, 'Table', {
  partitionKey: { name: 'id', type: dynamodb.AttributeType.STRING },
  encryption: dynamodb.TableEncryption.CUSTOMER_MANAGED,
  encryptionKey: new kms.Key(this, 'TableKey'),
});

CDK Insights pinpoints the exact file and line in your CDK source for every finding, so you can jump straight to the fix.

Affected resource types

AWS::DynamoDB::TableAWS::DynamoDB::GlobalTable

Compliance frameworks

SOC2HIPAAPCI-DSSNIST

AWS documentation

Read the AWS guidance

Intentional? Suppress this finding

Sometimes a flag is deliberate โ€” a genuinely public endpoint, say. You can dismiss dynamodb-encryption-aws-owned-key and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "dynamodb-encryption-aws-owned-key", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::dynamodb-encryption-aws-owned-key',
  reason: 'Why this is intentional',
});

Use the rule ID dynamodb-encryption-aws-owned-key shown above โ€” not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs โ†’

Catch this in your stack

$ npx cdk-insights scan

CDK Insights runs this and 118+ other rules locally against your synthesised CDK app โ€” free, no account, your code never leaves your machine.

More DynamoDB rules