New to Kestra?
Use blueprints to kickstart your first workflows.
Monitor Amazon DynamoDB throttled requests and capacity limits with Kestra. Query CloudWatch, open GitHub issues, and alert Slack.
Serverless NoSQL databases like Amazon DynamoDB automatically partition data across storage nodes. When hot partition keys or traffic spikes exceed provisioned Read/Write Capacity Units (or on-demand burst capacity), DynamoDB throttles requests, causing HTTP 400 ProvisionedThroughputExceededException errors to client microservices. This blueprint queries CloudWatch for ThrottledRequests metrics periodically, identifies capacity starvation, files a prioritized GitHub DBA ticket, and alerts the engineering team on Slack.
periodic_dynamodb_throttle_check runs every 15 minutes.probe_dynamodb_throttles queries CloudWatch for ThrottledRequests.evaluate_throttles evaluates if throttles exceed threshold.branch_on_throttles logs a GitHub issue and alerts Slack if breached.log_audit_complete logs final outcome.errors block alerts Slack on execution failure.Kestra provides declarative automation connecting CloudWatch metrics, conditional evaluation, and chat notifications in a single auditable flow.
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY: AWS credentials.GITHUB_TOKEN: GitHub token.SLACK_WEBHOOK: Slack webhook URL.aws_region: Target region.table_name: DynamoDB table name.throttle_threshold: Max throttles before alerting.target_repository: GitHub repository.outputs.evaluate_throttles.value.throttle_count: Number of throttles detected.outputs.evaluate_throttles.value.is_throttling_critical: Boolean breach flag.