AWS drift / remediation workspace
Inspect the fix before anything changes.
Three fixed scenarios. No AWS account connection, model API keys, or infrastructure changes.
Choose a scenario, then inspect its reviewer package.
S3 public access drift
View the synthetic input event
- 01TriageWaiting
- 02ImpactWaiting
- 03TerraformWaiting
- 04ValidateWaiting
- 05PolicyWaiting
- 06PR previewWaiting
Reviewer package
Not run yetYour proposed fix will appear here.
Inspect the impact, HCL, check evidence, and PR body. Human review and a plan in your own CI are still required.
Reconcile the proposal with existing resources and state. Review a Terraform plan, your organization's policies, and operational impact. The RDS sample is a standalone fixture, not a safe rollback for a production database.
Evaluate one real drift class with your team.
A pilot starts with a sandbox and an agreed baseline.
Opens a public GitHub issue draft. Do not include credentials, private repository links, account IDs, or production data. No signup or payment is created.
A configured backend submits only the fixed scenario name, uses mock LLM responses, and runs Terraform in Lambda. It may retain compact run metadata for 30 days. Public requests never open a GitHub PR.