Stack drift detection in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is stack drift in AWS CloudFormation?

Stack drift happens when the actual resources in your cloud environment change from what your CloudFormation template says they should be.

beginner

How does AWS CloudFormation detect stack drift?

It compares the current state of your resources with the expected state defined in your CloudFormation stack to find differences.

beginner

What types of changes can cause stack drift?

Manual changes outside CloudFormation, like updating a server or changing a security group directly in the AWS console, cause stack drift.

beginner

What is the benefit of detecting stack drift?

Detecting drift helps keep your cloud resources consistent with your templates, avoiding unexpected problems and making management easier.

beginner

Can AWS CloudFormation fix stack drift automatically?

No, CloudFormation only detects drift. You must update the stack or fix resources manually to correct the drift.

What does stack drift detection compare?

A User access logs

B Two different CloudFormation templates

C AWS billing reports

D Current resource state vs. CloudFormation template

Stack drift detection compares the actual state of resources with the expected state defined in the CloudFormation template.

Which action can cause stack drift?

A Updating resources manually outside CloudFormation

B Deploying a new CloudFormation stack

C Deleting a CloudFormation stack

D Creating a CloudFormation change set

Manual changes outside CloudFormation cause drift because they are not tracked by the template.

What should you do after detecting stack drift?

A Ignore the drift

B Delete the stack immediately

C Update the stack or fix resources manually

D Restart AWS services

After detecting drift, you must fix the resources or update the stack to match the desired state.

Does AWS CloudFormation automatically fix drift?

A Only if drift is minor

B No, it only detects drift

C Only for EC2 instances

D Yes, it fixes drift automatically

CloudFormation detects drift but does not fix it automatically.

Why is stack drift detection important?

A To keep resources consistent with templates

B To increase AWS billing

C To speed up deployments

D To backup data

Detecting drift helps maintain consistency and avoid unexpected issues.

Explain what stack drift is and how AWS CloudFormation detects it.

Think about how changes outside the template affect your stack.

Describe the steps you would take after detecting stack drift in your AWS environment.

Consider what actions keep your cloud environment healthy.

Practice

1.

What is the main purpose of stack drift detection in AWS CloudFormation?

easy

A. To find manual changes made outside of CloudFormation templates

B. To automatically fix errors in CloudFormation templates

C. To create new stacks from existing templates

D. To monitor network traffic between AWS resources

Solution

1. Step 1: Understand stack drift detection concept

   Stack drift detection checks if resources in a stack have been changed manually or outside CloudFormation management.

2. Step 2: Identify the main purpose

   The main goal is to find these manual or unexpected changes to keep infrastructure consistent.

3. Final Answer:

   To find manual changes made outside of CloudFormation templates -> Option A

4. Quick Check:

   Stack drift detection = find manual changes [OK]

Hint: Stack drift detection finds changes outside CloudFormation [OK]

Common Mistakes:

• Thinking it fixes errors automatically
• Confusing it with stack creation
• Assuming it monitors network traffic

2.

Which AWS CLI command starts drift detection for a CloudFormation stack named MyAppStack?

easy

A. aws cloudformation begin-drift-check --name MyAppStack

B. aws cloudformation detect-stack-drift --stack-name MyAppStack

C. aws cloudformation start-drift-detection --stack MyAppStack

D. aws cloudformation check-drift --stack-name MyAppStack

Solution

1. Step 1: Recall AWS CLI syntax for drift detection

   The correct command to start drift detection is detect-stack-drift with the --stack-name option.

2. Step 2: Match the command with the stack name

   aws cloudformation detect-stack-drift --stack-name MyAppStack uses the exact syntax and correct parameter for the stack name.

3. Final Answer:

   aws cloudformation detect-stack-drift --stack-name MyAppStack -> Option B

4. Quick Check:

   Detect drift command = detect-stack-drift [OK]

Hint: Use 'detect-stack-drift' with '--stack-name' to start detection [OK]

Common Mistakes:

• Using incorrect command verbs like start or begin
• Wrong parameter names like --stack or --name
• Mixing up command order or syntax

3.

After running aws cloudformation detect-stack-drift --stack-name MyStack, which command shows the drift detection status and results?

medium

A. aws cloudformation show-drift-results --stack-name MyStack

B. aws cloudformation get-stack-drift-status --stack-name MyStack

C. aws cloudformation list-stack-drift-detection --stack-name MyStack

D. aws cloudformation describe-stack-drift-detection-status --stack-drift-detection-id

Solution

1. Step 1: Identify the command to check drift detection status

   The AWS CLI command to check drift detection status is describe-stack-drift-detection-status.

2. Step 2: Confirm the correct parameter usage

   It requires the --stack-drift-detection-id parameter to specify the detection ID, not --stack-name.

3. Final Answer:

   aws cloudformation describe-stack-drift-detection-status --stack-drift-detection-id <detection-id> -> Option D

4. Quick Check:

   Check drift status = describe-stack-drift-detection-status [OK]

Hint: Use 'describe-stack-drift-detection-status' with detection ID to get drift results [OK]

Common Mistakes:

• Using non-existent commands like get-stack-drift-status
• Confusing list commands with status commands
• Wrong parameter names

4.

You ran aws cloudformation detect-stack-drift --stack-name TestStack but got an error: Stack with id TestStack does not exist. What is the most likely cause?

medium

A. The stack name is misspelled or the stack does not exist

B. Drift detection is not supported for this stack type

C. You need to add --region parameter to the command

D. The AWS CLI version is outdated and cannot run drift detection

Solution

1. Step 1: Analyze the error message

   The error says the stack with the given name does not exist, indicating a wrong name or missing stack.

2. Step 2: Consider other causes

   While region or CLI version issues can cause errors, this specific message points to a missing or misspelled stack name.

3. Final Answer:

   The stack name is misspelled or the stack does not exist -> Option A

4. Quick Check:

   Error about stack id means wrong or missing stack [OK]

Hint: Check stack name spelling and existence first [OK]

Common Mistakes:

• Assuming region parameter is always required
• Blaming CLI version without checking stack
• Ignoring the exact error message

5.

You want to ensure your CloudFormation stack stays consistent with its template. Which approach best uses stack drift detection to maintain this?

A) Run drift detection regularly and update stack if drift is detected.
B) Disable drift detection and manually check resources.
C) Use drift detection only after stack deletion.
D) Ignore drift detection and rely on CloudWatch alarms.

hard

A. Use drift detection only after stack deletion

B. Disable drift detection and manually check resources

C. Run drift detection regularly and update stack if drift is detected

D. Ignore drift detection and rely on CloudWatch alarms

Solution

1. Step 1: Understand drift detection best practice

   Regularly running drift detection helps find manual changes early and keeps the stack consistent.

2. Step 2: Evaluate options

   Run drift detection regularly and update stack if drift is detected uses drift detection proactively. Options B, C, and D either ignore drift detection or use it incorrectly.

3. Final Answer:

   Run drift detection regularly and update stack if drift is detected -> Option C

4. Quick Check:

   Regular drift detection = best practice [OK]

Hint: Run drift detection regularly to catch changes early [OK]

Common Mistakes:

• Ignoring drift detection completely
• Checking drift only after deletion
• Relying solely on CloudWatch for drift