Amazon DynamoDB controls
These controls are related to DynamoDB resources.
These controls may not be available in all AWS Regions. For more information, see Availability of controls by Region.
[DynamoDB.1] DynamoDB tables should automatically scale capacity with demand
Related requirements: NIST.800-53.r5 CP-10, NIST.800-53.r5 CP-2(2), NIST.800-53.r5 CP-6(2), NIST.800-53.r5 SC-36, NIST.800-53.r5 SC-5(2), NIST.800-53.r5 SI-13(5)
Category: Recover > Resilience > High availability
Severity: Medium
Resource type:
AWS::DynamoDB::Table
AWS Config rule:
dynamodb-autoscaling-enabled
Schedule type: Periodic
Parameters:
| Parameter | Description | Type | Valid custom values | Security Hub default value |
|---|---|---|---|---|
|
|
Minimum number of provisioned read capacity units for DynamoDB auto scaling |
Integer |
|
No default value |
|
|
Target utilization percentage for read capacity |
Integer |
|
No default value |
|
|
Minimum number of provisioned write capacity units for DynamoDB auto scaling |
Integer |
|
No default value |
|
|
Target utilization percentage for write capacity |
Integer |
|
No default value |
This control checks whether an Amazon DynamoDB table can scale its read and write capacity as needed. The control fails if the table doesn't use on-demand capacity mode or provisioned mode with auto scaling configured. By default, this control only requires that one of these modes be configured, without regard to specific levels of read or write capacity. Optionally, you can provide custom parameter values to require specific levels of read and write capacity or target utilization.
Scaling capacity with demand avoids throttling exceptions, which helps to maintain availability of your applications. DynamoDB tables in on-demand capacity mode are only limited by the DynamoDB throughput default table quotas. To raise these quotas, you can file a support ticket with AWS Support. DynamoDB tables in provisioned mode with auto scaling adjust the provisioned throughput capacity dynamically in response to traffic patterns. For more information about DynamoDB request throttling, see Request throttling and burst capacity in the Amazon DynamoDB Developer Guide.
Remediation
To enable DynamoDB automatic scaling on existing tables in capacity mode, see Enabling DynamoDB auto scaling on existing tables in theAmazon DynamoDB Developer Guide.
[DynamoDB.2] DynamoDB tables should have point-in-time recovery enabled
Related requirements: NIST.800-53.r5 CP-10, NIST.800-53.r5 CP-6(2), NIST.800-53.r5 CP-9, NIST.800-53.r5 SC-5(2), NIST.800-53.r5 SI-12, NIST.800-53.r5 SI-13(5)
Category: Recover > Resilience > Backups enabled
Severity: Medium
Resource type:
AWS::DynamoDB::Table
AWS Config rule:
dynamodb-pitr-enabled
Schedule type: Change triggered
Parameters: None
This control checks whether point-in-time recovery (PITR) is enabled for an Amazon DynamoDB table.
Backups help you to recover more quickly from a security incident. They also strengthen the resilience of your systems. DynamoDB point-in-time recovery automates backups for DynamoDB tables. It reduces the time to recover from accidental delete or write operations. DynamoDB tables that have PITR enabled can be restored to any point in time in the last 35 days.
Remediation
To restore a DynamoDB table to a point in time, see Restoring a DynamoDB table to a point in time in the Amazon DynamoDB Developer Guide.
[DynamoDB.3] DynamoDB Accelerator (DAX) clusters should be encrypted at rest
Related requirements: NIST.800-53.r5 CA-9(1), NIST.800-53.r5 CM-3(6), NIST.800-53.r5 SC-13, NIST.800-53.r5 SC-28, NIST.800-53.r5 SC-28(1), NIST.800-53.r5 SC-7(10), NIST.800-53.r5 SI-7(6)
Category: Protect > Data protection > Encryption of data at rest
Severity: Medium
Resource type:
AWS::DynamoDB::Cluster
AWS Config rule:
dax-encryption-enabled
Schedule type: Periodic
Parameters: None
This control checks whether a DAX cluster is encrypted at rest.
Encrypting data at rest reduces the risk of data stored on disk being accessed by a user not authenticated to AWS. The encryption adds another set of access controls to limit the ability of unauthorized users to access to the data. For example, API permissions are required to decrypt the data before it can be read.
Remediation
You cannot enable or disable encryption at rest after a cluster is created. You must recreate the cluster in order to enable encryption at rest. For detailed instructions on how to create a DAX cluster with encryption at rest enabled, see Enabling encryption at rest using the AWS Management Console in the Amazon DynamoDB Developer Guide.
[DynamoDB.4] DynamoDB tables should be present in a backup plan
Category: Recover > Resilience > Backups enabled
Related requirements: NIST.800-53.r5 CP-10, NIST.800-53.r5 CP-6, NIST.800-53.r5 CP-6(1), NIST.800-53.r5 CP-6(2), NIST.800-53.r5 CP-9, NIST.800-53.r5 SC-5(2), NIST.800-53.r5 SI-12, NIST.800-53.r5 SI-13(5)
Severity: Medium
Resource type:
AWS::DynamoDB::Table
AWS Config rule:
dynamodb-resources-protected-by-backup-plan
Schedule type: Periodic
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
|
|
The control produces a |
Boolean |
|
No default value |
This control evaluates whether an Amazon DynamoDB table in ACTIVE state is covered by a backup plan. The control
fails if the DynamoDB table isn't covered by a backup plan. If you set the backupVaultLockCheck
parameter equal to true, the control passes only if the DynamoDB table is backed up in an AWS Backup locked vault.
AWS Backup is a fully managed backup service that helps you centralize and automate the backing up of data across AWS services. With AWS Backup, you can create backup plans that define your backup requirements, such as how frequently to back up your data and how long to retain those backups. Including DynamoDB tables in your backup plans helps you protect your data from unintended loss or deletion.
Remediation
To add a DynamoDB table to an AWS Backup backup plan, see Assigning resources to a backup plan in the AWS Backup Developer Guide.
