AWS Config for compliance - Commands & Configuration

Introduction

AWS Config helps you track and check your cloud resources to make sure they follow rules you set. It solves the problem of knowing if your cloud setup is safe and follows company policies.

When you want to check if your cloud servers and storage follow security rules automatically.

When you need to see a history of changes made to your cloud resources for audits.

When you want alerts if someone changes a resource in a way that breaks your rules.

When you want to make sure your cloud setup matches compliance standards like PCI or HIPAA.

When you want to fix resource problems quickly by knowing exactly what changed and when.

Config File - config-rule.json

config-rule.json

{
  "ConfigRuleName": "s3-bucket-public-read-prohibited",
  "Description": "Checks that your S3 buckets do not allow public read access.",
  "Scope": {
    "ComplianceResourceTypes": ["AWS::S3::Bucket"]
  },
  "Source": {
    "Owner": "AWS",
    "SourceIdentifier": "S3_BUCKET_PUBLIC_READ_PROHIBITED"
  }
}

This JSON file defines a compliance rule for AWS Config.

ConfigRuleName: The name of the rule.

Description: What the rule checks.

Scope: Which resources the rule applies to (here, S3 buckets).

Source: The AWS managed rule to use for checking public read access on S3 buckets.

Commands

This command creates or updates the AWS Config rule using the JSON file. It tells AWS Config what rule to check for compliance.

Terminal

aws configservice put-config-rule --config-rule file://config-rule.json

Expected Output

{"ConfigRuleArn":"arn:aws:config:us-east-1:123456789012:config-rule/config-rule-abcdefg"}

→

--config-rule - Specifies the JSON file that defines the compliance rule.

This command checks the compliance status of the S3 bucket public read rule. It shows if your resources follow the rule or not.

Terminal

aws configservice describe-compliance-by-config-rule --config-rule-names s3-bucket-public-read-prohibited

Expected Output

{"ComplianceByConfigRules":[{"ConfigRuleName":"s3-bucket-public-read-prohibited","Compliance":{"ComplianceType":"COMPLIANT"}}]}

→

--config-rule-names - Specifies which rule's compliance status to show.

Key Concept

If you remember nothing else from this pattern, remember: AWS Config automatically checks your cloud resources against rules you set to keep your setup safe and compliant.

Common Mistakes

Using an incorrect JSON file path or format when creating the config rule.

The command fails because AWS Config cannot read or understand the rule definition.

Ensure the JSON file is valid, properly formatted, and the path is correct when running the command.

Not specifying the correct resource types in the rule scope.

The rule will not check the intended resources, so compliance results will be wrong or missing.

Include the exact AWS resource types you want the rule to evaluate in the Scope section.

Checking compliance immediately after creating the rule without waiting.

AWS Config needs time to evaluate resources; immediate checks may show no data or outdated status.

Wait a few minutes after creating the rule before checking compliance status.

Summary

Create an AWS Config rule using a JSON file to define compliance checks.

Use AWS CLI to apply the rule and start monitoring your resources.

Check compliance status with AWS CLI to see if your resources follow the rules.

Practice

1. What is the primary purpose of AWS Config in cloud management?

easy

A. To deploy applications automatically

B. To track changes in AWS resource configurations and check compliance

C. To monitor network traffic in real-time

D. To manage user permissions and roles

Solution

1. Step 1: Understand AWS Config's role

   AWS Config records configuration changes and evaluates compliance of AWS resources.

2. Step 2: Compare with other options

   Other options describe different AWS services like deployment, monitoring, or IAM, not AWS Config.

3. Final Answer:

   To track changes in AWS resource configurations and check compliance -> Option B

4. Quick Check:

   AWS Config = Compliance tracking [OK]

Hint: AWS Config = resource change tracking + compliance [OK]

Common Mistakes:

• Confusing AWS Config with deployment services
• Thinking AWS Config manages user permissions
• Mixing AWS Config with network monitoring tools

2. Which AWS Config component is responsible for recording resource configuration changes?

easy

A. Delivery Channel

B. Config Rule

C. Configuration Recorder

D. Compliance Pack

Solution

1. Step 1: Identify the component that records changes

   The Configuration Recorder captures resource configuration changes in AWS Config.

2. Step 2: Understand other components

   Config Rules evaluate compliance, Delivery Channel sends data to storage, Compliance Packs group rules.

3. Final Answer:

   Configuration Recorder -> Option C

4. Quick Check:

   Recorder = records changes [OK]

Hint: Recorder records changes; rules check compliance [OK]

Common Mistakes:

• Confusing Delivery Channel with recording
• Thinking Config Rule records changes
• Mixing Compliance Pack with recording function

3. Given this AWS Config rule JSON snippet, what does it check?

{
  "ConfigRuleName": "s3-bucket-public-read-prohibited",
  "Source": {
    "Owner": "AWS",
    "SourceIdentifier": "S3_BUCKET_PUBLIC_READ_PROHIBITED"
  }
}

medium

A. Checks if S3 buckets allow public read access

B. Checks if S3 buckets have versioning enabled

C. Checks if S3 buckets are encrypted

D. Checks if S3 buckets have lifecycle policies

Solution

1. Step 1: Analyze the SourceIdentifier

   The SourceIdentifier "S3_BUCKET_PUBLIC_READ_PROHIBITED" indicates the rule checks for public read access on S3 buckets.

2. Step 2: Match with options

   Checks if S3 buckets allow public read access matches the rule's purpose; others relate to different bucket settings.

3. Final Answer:

   Checks if S3 buckets allow public read access -> Option A

4. Quick Check:

   Rule name = public read check [OK]

Hint: Rule names often describe their check clearly [OK]

Common Mistakes:

• Assuming it checks encryption or versioning
• Ignoring the SourceIdentifier meaning
• Confusing lifecycle policies with access controls

4. You configured AWS Config but notice no compliance data is delivered. What is the most likely issue?

medium

A. Configuration Recorder is not started

B. Config Rules are disabled

C. IAM user lacks EC2 permissions

D. Delivery Channel is missing or misconfigured

Solution

1. Step 1: Understand data flow in AWS Config

   Configuration Recorder records changes; Delivery Channel sends data to S3 or SNS.

2. Step 2: Identify cause of no data delivery

   If no compliance data arrives, Delivery Channel is likely missing or misconfigured.

3. Final Answer:

   Delivery Channel is missing or misconfigured -> Option D

4. Quick Check:

   Delivery Channel = data delivery [OK]

Hint: Check Delivery Channel if no data arrives [OK]

Common Mistakes:

• Assuming Recorder is off without checking
• Confusing Config Rules with data delivery
• Blaming IAM permissions unrelated to Config

5. You want to enforce that all EC2 instances have a specific tag for cost center. Which AWS Config setup achieves this best?

hard

A. Create a Config Rule that checks EC2 instances for the required tag and alerts non-compliance

B. Use Configuration Recorder to record EC2 instance tags only

C. Set up Delivery Channel to send EC2 instance data to CloudTrail

D. Manually review EC2 instances weekly for tag compliance

Solution

1. Step 1: Identify enforcement method

   A Config Rule can automatically check EC2 instances for required tags and report compliance.

2. Step 2: Evaluate other options

   Recorder only records data, Delivery Channel sends data but doesn't enforce, manual review is inefficient.

3. Final Answer:

   Create a Config Rule that checks EC2 instances for the required tag and alerts non-compliance -> Option A

4. Quick Check:

   Config Rule = automatic compliance check [OK]

Hint: Use Config Rules to enforce resource settings automatically [OK]

Common Mistakes:

• Thinking Recorder enforces compliance
• Confusing Delivery Channel with enforcement
• Relying on manual checks instead of automation