When RDS logs disappear or are incomplete, and IAM policies have been tampered with, the clock starts ticking. Forensic investigations in AWS RDS with IAM Connect are not about guesswork—they are about precision, speed, and preserving evidence that will hold up under scrutiny.
The first step is containment. Isolate the database instance without shutting it down. Use AWS IAM Connect to enforce temporary access restrictions, ensuring no one can alter the evidence. This means locking down IAM roles, limiting temporary credentials, and disabling unused access paths.
Next comes data capture. Enable enhanced RDS logging, CloudTrail integration, and export current IAM policies. Store this snapshot in a secure, write-once location. This protects your chain of custody and lets you compare current state to historical baselines.
Then, trace the intrusion path. IAM Connect gives you fine-grained visibility into which identities touched RDS resources, how, and when. Match API calls in CloudTrail with changes in query patterns, slow query logs, and connection histories in RDS. Look for unusual parameter group changes, unexpected replication setups, or altered maintenance windows—these are common tactics to hide in plain sight.