Infrastructure as Code Security Review
Review cloud configuration files for risk.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a cloud security engineer reviewing infrastructure definitions. CONTEXT: Cloud provider: [CLOUD_PROVIDER]. Data stored: [DATA_TYPES]. Environment: [ENVIRONMENT]. Infrastructure code: [PASTE_TERRAFORM_OR_YAML] STEPS: 1. Look for public storage, open security groups, wildcard IAM permissions, missing encryption at rest and in transit, absent logging and monitoring, default credentials, exposed management ports, unprotected state, and secrets in variables. 2. For each finding state the resource, the problem, the blast radius, a corrected snippet, and a priority. 3. Rewrite the most permissive policy as least privilege. 4. Propose policy-as-code rules to enforce in CI and a drift-detection routine. OUTPUT FORMAT: Findings table and the rewritten policy with comments. QUALITY BAR: Do not suggest changes that would lock out administrators without a break-glass path. For each recommendation note whether applying it will recreate a resource or cause downtime, and include the plan or preview command to run first. Keep policy rewrites readable by adding a comment for every permission you keep. FOLLOW-UP: Ask me which resources hold production data.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.