opensite-ai/opensite-skills / aws-cloudformation
aws-cloudformation
UnverifiedAuthors, validates, and troubleshoots AWS CloudFormation templates. Covers template authoring with secure defaults, local validation with either cfn-lint or cloudformation-validate, cfn-guard security and compliance checks as a recommended default, account-aware CloudFormation service pre-deployment validation, CloudFormation Express mode for faster deployments, and root-cause diagnosis of failed stacks using CloudFormation events and CloudTrail correlation. Also covers author-time template intelligence with the CloudFormation Language Server and published cloudformation-validate libraries.
| File | Kind | Size |
|---|---|---|
| .aws-skill-metadata | other | 18 B |
| SKILL.md | skill md | 14.2 KB |
| references/author-cloudformation-best-practices.script.md | markdown | 8.9 KB |
| references/check-cloudformation-template-compliance.script.md | markdown | 7.9 KB |
| references/cloudformation-language-server.md | markdown | 8.1 KB |
| references/cloudformation-pre-deploy-validation.script.md | markdown | 19.5 KB |
| references/deploy-with-express-mode.script.md | markdown | 12.3 KB |
| references/lookup-resource-properties.script.md | markdown | 6.3 KB |
| references/persist-template-context.script.md | markdown | 14.4 KB |
| references/retrieve-template-context.script.md | markdown | 18.9 KB |
| references/security-considerations.md | markdown | 4.4 KB |
| references/template-safety-guidance.md | markdown | 8.1 KB |
| references/troubleshoot-deployment.script.md | markdown | 12.4 KB |
| references/troubleshoot-failed-stack.script.md | markdown | 9.1 KB |
| references/validate-with-cfn-lint.script.md | markdown | 7.8 KB |
| references/validate-with-cloudformation-validate.script.md | markdown | 9.2 KB |
| references/validation-tool-selection.md | markdown | 3.7 KB |
references/check-cloudformation-template-compliance.script.md
View on GitHub# Check CloudFormation Template Compliance
## Overview
Deterministic procedure for validating a CloudFormation template against security and compliance rules using cfn-guard. Works via the `cfn-guard` CLI or the Python `guardpycfn` library.
## Parameters
- **template_content** (required): The CloudFormation template as a YAML or JSON string, a file path, or a URL to the template.
- **rules_file_path** (optional): Path to a custom cfn-guard rules file. If omitted, you MUST obtain rules separately because cfn-guard has no built-in rule set. Recommended source: https://github.com/aws-cloudformation/aws-guard-rules-registry
**Constraints for parameter acquisition:**
- You MUST ask for all required parameters upfront in a single prompt rather than one at a time
- You MUST support multiple input methods for the template:
- Direct input: Template content pasted directly
- File path: Path to a local template file
- URL: Link to a template in a repository or S3
- You MUST confirm successful acquisition of the template content before proceeding
## Steps
### 1. Verify Dependencies
Check which compliance mechanism is available.
**Constraints:**
- You MUST check in this order of preference:
1. `cfn-guard` CLI available on the user's system (verify with `which cfn-guard` or `cfn-guard --version`)
2. Python `guardpycfn` library (verify by attempting `import guardpycfn` in a throwaway Python command)
- If cfn-guard is not installed, You MUST ask the user: "I can install `cfn-guard` (see https://docs.aws.amazon.com/cfn-guard/latest/ug/setting-up.html for install options). Do you want me to install it, or would you prefer to install it manually?"
- You SHOULD run the compliance check by default when a supported mechanism is available; You MUST NOT run an install command without the user's explicit approval because installation changes the user's environment
- If no mechanism is available and the user declines installation, You MUST ask whether to abort or proceed anyway (knowing the SOP cannot complete)
- You MUST respect the user's decision to proceed, install, or abort
### 2. Acquire Template Content
Obtain the CloudFormation template from the user.
**Constraints:**
- You MUST ask the user which template(s) to check even if templates are discoverable in the working directory, because the user may only want a subset checked
- You MUST read the template content from the provided source (file path, direct input, or URL)
- You MUST confirm the template is non-empty and parseable as YAML or JSON before proceeding
- If the template cannot be read or parsed, You MUST inform the user with the specific error and stop
- You SHOULD recommend running the project-selected local validation SOP first if the user has not already done so: either the [cfn-lint SOP](validate-with-cfn-lint.script.md) or the [cloudformation-validate SOP](validate-with-cloudformation-validate.script.md), never both by default, because compliance checks assume a syntactically valid template
### 3. Acquire Rules File (if needed)
Determine which rules to apply.
**Constraints:**
- If the CLI or `guardpycfn` library is used, You MUST obtain a rules file because cfn-guard requires explicit rules:
- If the user provided `rules_file_path`, You MUST use it
- Otherwise, You MUST recommend the user download the AWS managed rules from https://github.com/aws-cloudformation/aws-guard-rules-registry
- You MUST confirm the rules file is readable before proceeding
### 4. Run Compliance Check
Execute cfn-guard against the template using the best available mechanism.
**Constraints:**
- If `cfn-guard` CLI is available, You MUST invoke it with the template and rules file:
- Example: `cfn-guard validate --rules rules.guard --data template.yaml --output-format json`
- You MUST use `--output-format json` for structured output
- Otherwise, if the Python `guardpycfn` library is available, You MUST invoke `guardpycfn.validate_with_guard(template_content, rules_content, verbose=True)`
- You MUST NOT modify the template content before checking because the user needs to see violations against their actual template
- You MUST capture the full output including rule IDs, resource names, resource types, and remediation messages
### 5. Present Results
Report compliance findings to the user.
**Constraints:**
- You MUST start the summary with: "Your template has X violations"
- You MUST group related violations together (e.g., all PublicAccessBlock settings for an S3 bucket)
- You MUST prioritize by severity: critical security issues first (encryption, public access), then best-practice recommendations (versioning, logging, replication)
- For repeated sub-property violations on the same resource, You MUST show them once: "Settings (A, B, C, D) must all be true"
- You MUST add context for optional features (e.g., ObjectLock and Replication may not be needed for all use cases)
- For each violation, You MUST provide the specific CloudFormation properties to add or change
- You MUST use inline YAML comments to explain why each property is needed
- You MUST NOT show entire resource definitions when only specific properties need to change
- If the template is fully compliant, You MUST confirm this clearly
### 6. Recommend Next Steps
Guide the user after compliance results.
**Constraints:**
- If critical security violations were found, You MUST recommend fixing them before deployment
- You SHOULD help the user understand which violations are mandatory fixes versus optional improvements based on their use case
- After fixes are applied, You SHOULD recommend re-running this SOP to confirm all violations are resolved
- Once compliance passes, You SHOULD recommend the `cloudformation-pre-deploy-validation` SOP for final pre-deployment readiness
## Security Considerations
Follow the [shared security guidance](security-considerations.md) when handling templates, outputs, secrets, tools, and installation artifacts.
## Examples
### Example Input
```yaml
AWSTemplateFormatVersion: '2010-09-09'
Resources:
MyBucket:
Type: AWS::S3::Bucket
Properties:
BucketName: my-app-data
```
### Example Output
```
Your template has 4 violations.
**MyBucket (AWS::S3::Bucket) — Critical Security:**
1. Public access not blocked. Add:
PublicAccessBlockConfiguration:
BlockPublicAcls: true # Prevents public ACLs
BlockPublicPolicy: true # Prevents public bucket policies
IgnorePublicAcls: true # Ignores existing public ACLs
RestrictPublicBuckets: true # Restricts public bucket access
2. Server-side encryption not configured. Add:
BucketEncryption:
ServerSideEncryptionConfiguration:
- ServerSideEncryptionByDefault:
SSEAlgorithm: aws:kms # KMS encryption at rest
**MyBucket (AWS::S3::Bucket) — Best Practice:**
3. Versioning not enabled. Add:
VersioningConfiguration:
Status: Enabled # Protects against accidental deletes
4. Access logging not configured. Add:
LoggingConfiguration:
DestinationBucketName: !Ref LogBucket
**Advisory — Optional Enhancements:**
ObjectLock and Replication rules also flagged. Evaluate based on your use case before adding.
```
## Troubleshooting
### High violation count on simple templates
Some rules check multiple sub-properties independently. A single missing `PublicAccessBlockConfiguration` block can produce 4 separate violations (one per sub-property). Group them mentally and fix the parent property.
### False positives for optional features
Rules like `S3_BUCKET_REPLICATION_ENABLED` and `S3_BUCKET_DEFAULT_LOCK_ENABLED` enforce best practices that may not apply to every bucket. Evaluate whether the feature is needed for your use case before adding it.
### Custom rules not found
If using a custom `rules_file_path`, ensure the file exists and follows cfn-guard rule syntax. Standalone CLI and `guardpycfn` usage both require obtaining rules separately (e.g., from the aws-guard-rules-registry).
### cfn-guard not installed
Install from https://docs.aws.amazon.com/cfn-guard/latest/ug/setting-up.html.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |