cfn-python-lint
cloudformation-resource-providers
Our great sponsors
| cfn-python-lint | cloudformation-resource-providers | |
|---|---|---|
| 20 | 1 | |
| 2,342 | 12 | |
| 0.9% | - | |
| 9.1 | 4.3 | |
| 6 days ago | 1 day ago | |
| Python | Python | |
| MIT No Attribution | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cfn-python-lint
-
Deploy config rules across your organization
Now the first 3 options are pretty straight forward. The template itself is a bit more complicated. In my example I used an inline template, I did this for the sake of this blog. But you can also reference an existing object on S3. This way you can use linting tools like cfn-lint on your conformance pack. This will reduce errors during deployment as you can catch them before you commit and push your code.
-
Managing low-code environments with AWS CloudFormation and Azure Resource Manager
Automate testing and validation: Before deploying your templates, it's important to test and validate them to ensure that they will work as expected. Use tools like AWS CloudFormation Linter and Azure Resource Manager Template Tester to automate this process.
-
Alternatives to Terraform
Honestly I've had good luck writing clean Cloud Formation. It's AWS only. But Nested Stacks can help keep things pretty clean and tools like cfn-lint do a pretty good job of preventing you from going too crazy with spaghetti code. Additionally, as it's all json/yaml, you can parse it to look for common problems your organization wants to enforce. So you can ensure things like specific tags your roles/vpc etc..., or usage of an "approved" set of AMI, requiring an EKS/RDS cluster to be split across availability zones; they're all just a test in your CI pipeline away.
-
Creating a Multi-Account CI/CD Pipeline with AWS CodePipeline
CodeBuild will run a linting check against the CloudFormation Template using cfn-lint and will then run cfn-nag to check for patterns that indicate insecure resources within the CloudFormation template.
-
App with self-contained infrastructure on AWS
A linter for our AWSCloudformation stack called cfn-lint
-
how did you get good at iac-cloudformation
cfn-lint and cfn_nag or other tools of that nature to check as you write so you don't need to continually try to deploy only to find that you've done something dumb.
-
Validating cloudFormation templates
https://github.com/aws-cloudformation/cfn-lint as mentioned will do what you've explicitly called-out.
-
CloudFormation locally
cfn-lint can do basic validation and rule-based linting. Highly recommend using it even if it doesn't solve your problem.
-
Source Control your AWS CloudFormation templates with GitHub
To help validate your AWS CloudFormation templates you can use a tool called cfn-lint.
cloudformation-resource-providers
What are some alternatives?
cfn_nag - Linting tool for CloudFormation templates
troposphere - troposphere - Python library to create AWS CloudFormation descriptions
aws-codebuild-docker-images - Official AWS CodeBuild repository for managed Docker images http://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref.html
ecs_composex - Manage, Configure and Deploy your services and AWS services and applications from your docker-compose definitions
cloudformation-guard - Guard offers a policy-as-code domain-specific language (DSL) to write rules and validate JSON- and YAML-formatted data such as CloudFormation Templates, K8s configurations, and Terraform JSON plans/configurations against those rules. Take this survey to provide feedback about cfn-guard: https://amazonmr.au1.qualtrics.com/jfe/form/SV_bpyzpfoYGGuuUl0
aws-resource-providers - A community driven repository where you can find AWS Resource Type Providers for different purposes (including org-formation ones).
terraform-aws-icons - Annotate Terraform graphs with AWS icons.
cloudformation-cli - The CloudFormation Provider Development Toolkit allows you to author your own resource providers and modules that can be used by CloudFormation.
aws-toolkit-vscode - Amazon Q, CodeWhisperer, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
rain - A development workflow tool for working with AWS CloudFormation.
aws-iam-generator - Generate Multi-Account IAM users/groups/roles/policies from a simple YAML configuration file and Jinja2 templates.
terraforming - Export existing AWS resources to Terraform style (tf, tfstate) / No longer actively maintained