Auto-trigger docker build for cfn-nag when new release is announced
100K+
Auto-trigger docker build for Linting tool for CloudFormation templates when new release is announced
The latest docker tag is the latest release verison (https://github.com/cfn-nag/cfn-nag/releases/latest)
Please avoid to use latest tag for any production deployment. Tag with right version is the proper way, such as alpine/cfn-nag:0.5.33
https://github.com/alpine-docker/cfn-nag
https://travis-ci.org/alpine-docker/cfn-nag
https://hub.docker.com/r/alpine/cfn-nag/tags/
# mount local folders in container.
docker run -ti --rm -v $(pwd):/apps -w /apps alpine/cfn-nag --input-path .
# run container as command
alias cfn_nag_scan="docker run -ti --rm -v $(pwd):/apps -w /apps alpine/cfn-nag"
cfn_nag_scan --help
--------
| WARN W47
|
| Resources: ["SNSAllConfigurationTopic", "SNSNotification"]
| Line Numbers: [45, 76]
|
| SNS Topic should specify KmsMasterKeyId property
------------------------------------------------------------
| FAIL F5
|
| Resources: ["AdditionalManagedIAMPolicy"]
| Line Numbers: [42]
|
| IAM managed policy should not allow * action
------------------------------------------------------------
https://stelligent.com/2018/03/23/validating-aws-cloudformation-templates-with-cfn_nag-and-mu/
Mostly it is used during CI/CD (continuous integration and continuous delivery) or as part of an automated build/deployment
alpine/cfn-nag:latest and push to hub.docker.comContent type
Image
Digest
Size
33.9 MB
Last updated
over 4 years ago
docker pull alpine/cfn-nagPulls:
182
Last week