Shield Agent AI

All replays

Vendor replays

Coding agent risks with AWS: replays and fixes

3 replays involve AWS: 0 reported incidents and 3 command classes. Each one shows the call, a fix that needs no extra tool, and what KYA did in the replay.

  • AWS RDS instance deletion

    Fix: Turn on deletion protection for the instance with aws rds modify-db-instance --db-instance-identifier NAME --deletion-protection (for Aurora, modify the cluster), so a delete fails until a person turns it off. Give the agent an IAM role that allows neither rds:DeleteDBInstance nor rds:ModifyDBInstance, which can turn the protection off, and keep manual snapshots, which RDS does not delete with the instance.

    Replay result: Stopped.

  • AWS S3 bucket removal with force

    Fix: Turn on S3 Versioning, so a delete leaves earlier versions that you can restore, and use Object Lock in compliance mode only for data you must keep, because nobody can shorten or remove it until the retention ends. Give the agent an IAM role that does not allow s3:DeleteBucket, s3:DeleteObject, s3:DeleteObjectVersion or s3:BypassGovernanceRetention (which overrides governance mode only).

    Replay result: Stopped.

  • Write an AWS access key id into a deploy script

    Fix: Use IAM roles or IAM Identity Center (aws sso login), so scripts need no static access key. If a key reached a file, deactivate and rotate it in IAM.

    Replay result: Stopped.

All replays

Does a client ask how you control AI coding agents?

The Answer Pack drafts your answers to the AI section of a client security questionnaire.

Get the Answer Pack