Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
dynamodb_accelerator_cluster_in_transit_encryption_enabledProvider: AWS
Service:
dynamodbSeverity: MEDIUM
Categories:
encryptionResource type:
OtherWhat this check verifies
DAX clusters have endpoint encryption set toTLS, enforcing encryption in transit for client connections to the cluster
Risk
Missing TLS enables interception and manipulation of DAX traffic, impacting:- Confidentiality: exposure of queries, data, or credentials
- Integrity: tampered requests/responses and cache poisoning
- Availability: session hijacking or replay causing service disruption
Recommendation
Enforce TLS for all DAX endpoints and clients (encryption in transit). If an existing cluster lacks it, create a new TLS-enabled cluster and migrate.
Apply defense in depth: restrict network paths, keep access private, and use least privilege IAM to reduce blast radius.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws dax create-cluster —cluster-name <cluster-name> —node-type <node-type> —replication-factor <replication-factor> —cluster-endpoint-encryption-type TLS
References
- https://docs.aws.amazon.com/securityhub/latest/userguide/dynamodb-controls.html#dynamodb-7
- https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DAXEncryptionInTransit.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = dynamodb_accelerator_cluster_in_transit_encryption_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks