AWS Config for compliance - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is AWS Config?

AWS Config is a service that records and tracks changes to your AWS resources, helping you understand resource configurations and compliance over time.

beginner

How does AWS Config help with compliance?

AWS Config continuously monitors and records your AWS resource configurations and compares them against rules to check if they comply with your policies.

beginner

What is an AWS Config rule?

An AWS Config rule is a set of conditions that AWS Config uses to evaluate whether your AWS resources comply with your desired configurations.

intermediate

What happens when a resource is non-compliant in AWS Config?

AWS Config flags the resource as non-compliant and can trigger notifications or automated actions to help you fix the issue.

beginner

Can AWS Config track changes over time?

Yes, AWS Config keeps a history of resource configurations, so you can see how your resources changed and when, which helps in audits and troubleshooting.

What does AWS Config primarily do?

A Manages user access permissions

B Tracks and records AWS resource configurations

C Deploys applications automatically

D Monitors network traffic

AWS Config tracks and records the configurations of AWS resources to help with compliance and auditing.

What is the purpose of an AWS Config rule?

A To evaluate resource compliance against policies

B To deploy new AWS resources

C To monitor application performance

D To backup data automatically

AWS Config rules evaluate whether your AWS resources meet your defined compliance policies.

If a resource is non-compliant, what can AWS Config do?

A Automatically delete the resource

B Ignore the resource

C Flag the resource and notify you

D Change the resource configuration automatically

AWS Config flags non-compliant resources and can notify you to take action.

Which of these is NOT a feature of AWS Config?

A Real-time application monitoring

B Resource configuration history

C Compliance evaluation

D Automated remediation triggers

AWS Config does not monitor application performance; it focuses on resource configurations and compliance.

How does AWS Config help during audits?

A By scaling resources automatically

B By encrypting all data automatically

C By blocking unauthorized users

D By providing a history of resource configurations

AWS Config provides a detailed history of resource configurations, which is useful for audits.

Explain how AWS Config supports compliance management in AWS environments.

Think about monitoring, rules, and history.

Describe what an AWS Config rule is and how it works.

Focus on evaluation and compliance.

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