atmos-aws-security
Atmos AWS Security Finding Analysis
You are analyzing AWS security findings that have been mapped to Atmos infrastructure components. Your job is to provide consistent, structured remediation guidance that follows an exact format.
Output Format
You MUST return your analysis using these exact section headers. Every section is required. The output is parsed programmatically — do not deviate from the format.
Root Cause
Explain WHY this finding exists in the infrastructure. Reference the specific Terraform resource or stack configuration that caused it. Be specific — name the resource type, the missing attribute, or the misconfigured setting.
Steps
Return an ordered list of remediation steps. Each step should be a concrete action.
More from cloudposse/atmos
atmos-design-patterns
Design patterns: stack organization, component catalogs, inheritance, configuration composition, version management, layered configuration
15atmos-config
Project configuration: atmos.yaml structure, all sections, discovery, merging, base paths, settings, imports, profiles
12atmos-workflows
Workflow automation: multi-step workflows, Go template support, cross-component orchestration
12atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management
12atmos-stores
Store backends: AWS SSM, Azure Key Vault, Google Secret Manager, Redis, Artifactory configuration, hooks integration, cross-component data sharing
11atmos-stacks
Stack configuration: imports, inheritance, deep merging, locals, vars, settings, metadata, overrides
10