The Cloudrail CLI container is meant to be used in conjunction with the Cloudrail Web UI. If you have not yet registered through the Web UI, please do so first.
As part of Cloudrail’s analysis operations, Cloudrail’s CLI makes use of some of the data from Terraform plan file. We filter the file from sensitive information (e.g. IP addresses, credentials, etc) and upload it to the Cloudrail Service for analysis. After analysis, the file is removed from the Service (that is, it is not kept beyond the time of analysis).
The following instructions assume that you are running Cloudrail in an environment that can run
If your Terraform plan files are only available through your CI/CD pipeline (e.g. a Jenkins server or a hosted CircleCI instance), then you will want to read our instructions for evaluating IaC from your pipeline. We recommend running an evaluation this way.
- Docker execution environment (such as Docker Desktop)
- Fetch the API key for your Cloudrail account in Cloudrail Web UI:
- Change your working directory to where your Terraform code is located. Generate a plan and save it, like so:
terraform plan -out=plan.out
- When running Cloudrail on your own workstation, we recommend saving the API key to the container’s
cloudrailvolume, like so:
docker run --rm -it -v $PWD:/data -v cloudrail:/indeni indeni/cloudrail-cli config set api_key=<API_KEY_FROM_WEB_UI>
- Run the Cloudrail container with the plan file:
docker run --rm -it -v $PWD:/data -v cloudrail:/indeni indeni/cloudrail-cli run -p plan.out
During this step, Cloudrail will provide an interaction to ask you a couple things. In the future, you can provide flags to automatically answer them:
- To specify the parent directory of all your Terraform files, use '-d' as a flag for 'cloudrail run' like so:
docker run --rm -it -v $PWD:/data indeni/cloudrail-cli run -p plan.out -d .
- To auto-approve the filtered plan that Cloudrail generated from your Terraform plan, use '--auto-approve':
docker run --rm -it -v $PWD:/data indeni/cloudrail-cli run -p plan.out --auto-approve --api-key <API_KEY_FROM_WEB_UI>
- If you would like to first generate the filtered plan, then review it (with a script, for example), and then upload it, start with the
generate-filtered-plancommand, and the pass it to
docker run --rm -it -v $PWD:/data indeni/cloudrail-cli generate-filtered-plan --output-file filteredplan.json
docker run --rm -it -v $PWD:/data indeni/cloudrail-cli run --filtered-plan filteredplan.json --api-key <API_KEY_FROM_WEB_UI>
-v $PWD:/dataparameter is required, as it gives the container access to your Terraform files for analysis.
- You can set an environment variable called
CLOUDRAIL_API_KEYor pass a
--api-keyparameter, instead of using