cloudig, or Cloudigest, is a simple CLI tool for creating reports from various cloud sources with user-provided comments. It is written in Go and currently uses AWS APIs to generate reports based on five pillars — operational excellence, security, reliability, performance efficiency, and cost optimization. CLI allows users to provide comments for documenting exceptions and work in progress. This report can be useful in various use cases such as a quality gate step in IaC CI/CD pipeline, daily monitoring for operations to keep account status of multiple accounts in green status, single source for enterprise security/compliance teams to endorse the accounts, etc.

The currently supported cloud sources are:

  • AWS IAM Reflect: This custom source uses CloudTrail for event history of AWS IAM role activity and IAM to compare the actual permissions.
  • AWS Trusted Advisor: Provides real time guidance to help provision resources following AWS best practices. 100+ checks on cost optimization, security, fault tolerance, performance, and service limits
  • AWS Config: Continuously monitors and records our AWS resource configurations and allows us to automate the evaluation of recorded configurations against desired configurations. This module can help enable AWS Config with the desired configuration baseline.
  • AWS Inspector: Automatically assesses applications running in EC2 instances for exposure, vulnerabilities, and deviations from best practices. After performing an assessment, Amazon Inspector produces a detailed list of security findings prioritized by level of severity.
  • AWS ECR Scan : Provides image scanning to identify software vulnerabilities in container images.
  • AWS Health Notifications: Provides relevant and timely information to help manage events in progress, and provides proactive notification to help you plan for scheduled activities.




cloudig can be installed two ways:

  1. Downloading latest release binary:



    curl -LO
    && tar -xf cloudig
    _.tar.gz cloudig
    && chmod +x cloudig
    && mv cloudig /usr/local/bin
    && cloudig --help

  2. Cloning repo and running make build NOTE: must have Go installed

    git clone

    cd cloudig

    make build

    ./cloudig --help

CLI Verbs

get - Get reports. Get ready-made reports directly from sources like Trusted Advisor, ECR scan, etc.

reflect - Reflect on resources. Custom reports based on past usage and current configurations. Ex: Reflect on IAM role usage.

Global Flags

--help,-h : Generate help documentation

--version : Prints version of the CLI

--rolearn: (Optional) Takes the comma separated list of role ARN's. Provided role must have minimum permission needed to pull findings from AWS sources. Also, your parent account must have trust relationship so it can assume the role. When no role is provided, findings are only from the account associated with provided credentials

--cfile, -c: (Optional) YAML file to provide user comments for each finding. When this file is not provided, each finding is treated as a new finding

--region, -r: (Optional) AWS region to get results from. Default is us-east-1

--output, -o: (Optional) Output of the report. Options: json, table, and mdtable. Default is JSON

--verbose, -v: (Optional) set log level, use 0 to silence, 1 for critical, 2 for warning, 3 for informational, 4 for debugging and 5 for debugging with AWS debug logging (default 3)

IAM Reflect source specific flags

--identity, -i: (Optional) One or more IAM Identities (users, groups, and roles) ARNs separated by a comma [,]. Only role ARN is supported today

--identity-tags, -t: (Optional) Set of tags in form [key:value] separated by [,] to find the targeted IAM Identities. Only role ARNs is supported today. Ignored when --identity is provided

--usage, -u : (Optional) Reflect Identity usage data (default true, if --errors/-e is not explicitly provided)

--errors, -e : (Optional) Reflect Identity error data (default true, if --usage/-u is not explicitly provided)

--caller-identity : (Optional) Include caller identity with the report(default false)

--absolute-time : (Optional) Specify both the start and end times for the time filter in the form 'startTime-endTime' 'mm/dd/yyyy-mm/dd/yyy' ex: '10/25/2020-10/31/2020'

--relative-time : (Optional) Specify a time filter relative to the current time in days. Default 1 day. Ignored when absolute-time is provided

Health source specific flags

--details, -d: (Optional) Health event descriptions are often very long, thus, by default, it is shortened to three sentences. If this flag is added, then the entire description is printed out.

--pastdays: (Optional) Number of past days to get results from. Default is all health events that are open / upcoming.

Source specific examples:


Even though the goal of "IAM reflect" is following the "Principle of least privilege" by keeping "Configured Permissions" equal to "Actual used Permissions", it is not always possible. This is mainly because some of the API actions for various AWS services are not tracked in CloudTrail, such as S3 & CloudWatch data events. Also, in some cases, API actions are named slightly differently. Don't let the perfect be the enemy of the good. Use this wisely! More info 1 & 2

Reflect uses CloudTrail event data stored in S3 and currently assumes partitions in the form ${Trail log location}/${region}/${year}/${month}/${day}. It returns zero results if it doesn't find the necessary partitions. We should be able to support different partition schemes in future releases.

Comment file(cfile):

Comment file provides a way to pass in user comments to findings from various sources. By default, CLI looks for the file name 'comments.yaml' to parse the comments. User can also provide a different location by using flag --cfile or -c

Below is the sample file:

- accountid: "111111111111"
    - SECURITY-IAM_Use: "**EXCEPTION:** We use Federation and IAM roles to manage resources in AWS . No users/groups created in IAM"
    - IAM_POLICY_BLACKLISTED_CHECK: "**EXCEPTION:** Removed the AdministratorAccess policy since the default AWS_*_Admins uses the policy. Future enhancement would be to create a Custom Rule that no other Role can use the AdministratorAccess policy besides the AWS_*_Admins"
    - CIS_Operating_System_Security_Configuration_Benchmarks-1.0: "**EXCEPTION:*** Description here"

IAM permission requirements

Sample Policy needed to run cloudig and ability to use assume role to run report across multiple accounts:

data "aws_iam_policy_document" "cloudig_policy" {
  statement {
    effect = "Allow"

    actions = [
    resources = ["*"]

data "aws_iam_policy_document" "cloudig_assume_role" {
  statement {
    effect = "Allow"

    actions = [

    principals {
      type        = "AWS"
      identifiers = ["arn:aws:iam::111111111111:role/AWS_111111111111_Read"]

resource "aws_iam_role" "cloudig_role" {
  name               = "cloudig"
  assume_role_policy = data.aws_iam_policy_document.cloudig_assume_role.json

resource "aws_iam_role_policy" "cloudig_policy" {
  name   = "cloudig"
  role   =
  policy = data.aws_iam_policy_document.cloudig_policy.json

Note: Support doesn't let you allow or deny access to individual actions. Therefore, the Action element of a policy is always set to support:_. Similarly, Support & Inspector don't provide resource-level access, so the Resource element is always set to _. Need access to EC2 for getting AMI information

Developer Notes


cloudig uses the Go Modules support built into Go 1.11. Make sure installed go version is at least 1.11

go build -o cloudig OR make build

Build for different Target OS and Platform:

env GOOS=<target-OS> GOARCH=<target-architecture> go build -o cloudig


make compile

  • This will compile the 64-bit binaries for Linux, Windows, and Mac


Running the tests: make test

Validating the test coverage :

go test -v -coverprofile cover.out

go tool cover -html=cover.out // opens a html output in default browser

Testing methodology:

cloudig tests are written using the GoMock mocking framework and table-driven tests.

A few of the reasons we chose to use GoMock are:

  1. Allows us to write tests for functions that make API calls without actually making the call.
  2. Integrates well with the standard library testing package: testing.

Examples of these tests can be found under the pkg/aws and pkg/cloudig folders

The mocks that were generated can be found under the pkg/mocks folder and the commands used to generate them can be found here


This project uses a very simple but effective logger library that allows us to set a different logging level with the flag --verbose or -v. Different levels are 1 for critical, 2 for warning, 3 for informational, 4 for debugging, and 5 for debugging with AWS debug logging with the default being 3 (informational).

  • Files supporting commands in package cmd and controller logic in package cloudig are instrumented to log at a different level.
  • AWS interactions in package aws are purposefully kept out of adding more logging as we can always use -v5 to enable AWS SDK debug logging. All methods in AWS client is expected to promptly propagate the error back to the caller to avoid duplicate logging.