Apache Pulsar multi-tenant backlog quarantine and priority event router
Drain a multi-tenant Pulsar topic and route each batch by tenant priority tier, logging ENTERPRISE traffic and quarantining the rest, with a Slack report per run.
Automate Amazon RDS manual snapshots with Kestra, nightly creation, retention-based pruning to cut storage costs, and Slack reporting.
Manual RDS snapshots are the safety net every team wants and nobody maintains. Someone creates them before a migration, then they pile up for months, quietly adding to the AWS bill while nobody knows which ones are still needed. This blueprint turns snapshot hygiene into a scheduled, auditable flow.
db_instance_identifiers and creates one timestamped manual snapshot per instance via the AWS CLI.SnapshotCreateTime against the retention cutoff, and deletes anything older.instance-20261017-0100) that sort chronologically.Platform engineers, DBAs, and DevOps teams running Amazon RDS in production who are tired of paying for forgotten snapshots.
A cron job on one EC2 instance is invisible and unmonitored. As a Kestra flow you get retries on transient AWS API failures, per-task logs, execution history, and a single place where the whole team can see last night's rotation, plus inputs like retention_days editable without touching code.
rds:CreateDBSnapshot, rds:DeleteDBSnapshot, and rds:DescribeDBSnapshots permissions.AWS_ACCESS_KEY_ID: AWS access key for the RDS API calls.AWS_SECRET_ACCESS_KEY: AWS secret key for the RDS API calls.SLACK_WEBHOOK_URL: Incoming webhook URL for the run summary.db_instance_identifiers to your RDS instances and retention_days to your policy (default 7).rds wait db-snapshot-available) before pruning for strict ordering.rds copy-db-snapshot.