DynamoDB CloudWatch Alarm Tables

Monitoring of count of Read/Write throttling is useful on table (its indexes) level. Each DynamoDB table and its GSI have their own provisioned capacity (Read/Write) and does not affect operation on other tables within same account. Can you share details of your use case, why do you want to setup one alarm for all tables within your account? I will be able to make some recommendations accordingly.

To get specific, you can imagine I can have 2 alarms (foo and bar) which are identical except for the TableName value. I guess I was hoping it's possible to merge this alarms to minimize repeating configuration setup.

aws cloudwatch put-metric-alarm \
--alarm-actions arn:aws:sns:us-west-2:numbers:details \
--alarm-description "Alarm trigger when ConsumedWriteCapacityUnits > ProvisionedWriteCapacityUnits" \
--alarm-name ims-dynamodb-high-write-units-foo \
--comparison-operator GreaterThanThreshold \
--dimensions Name=TableName,Value=foo \
--evaluation-periods 1 \
--metric-name ConsumedWriteCapacityUnits \
--namespace AWS/DynamoDB \
--period 60 \
--region us-west-2 \
--statistic Average \
--threshold 500 \
--treat-missing-data notBreaching

aws cloudwatch put-metric-alarm \
--alarm-actions arn:aws:sns:us-west-2:numbers:details \
--alarm-description "Alarm trigger when ConsumedWriteCapacityUnits > ProvisionedWriteCapacityUnits" \
--alarm-name ims-dynamodb-high-write-units-bar \
--comparison-operator GreaterThanThreshold \
--dimensions Name=TableName,Value=bar \
--evaluation-periods 1 \
--metric-name ConsumedWriteCapacityUnits \
--namespace AWS/DynamoDB \
--period 60 \
--region us-west-2 \
--statistic Average \
--threshold 500 \
--treat-missing-data notBreaching