aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

[AWS::KMS::Alias] implement `drift detection`

Open
#1,672 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::KMS::Alias

### Resource Name

_No response_

### Issue Description

[AWS::KMS::Alias](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kms-alias.html) does not support drift detection.

[Resource supported for drift detection](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/resource-import-supported-resources.html).

### Expected Behavior

[AWS::KMS::Alias] included in drift detection results.

### Observed Behavior

[AWS::KMS::Alias] is NOT included in drift detection results.

### Test Cases

```
key = Key(self, "MyKey",
removal_policy=RemovalPolicy.DESTROY
)

key.add_alias("alias/foo")
key.add_alias("alias/bar")
```

```aws cloudformation detect-stack-drift --stack-name KmsStack```
```aws cloudformation describe-stack-resource-drifts --stack-name KmsStack```

```StackResourceDrifts: []```

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the AWS::KMS::Alias example in the issue and run the listed aws cloudformation detect-stack-drift and describe-stack-resource-drifts commands against the stack. Compare the empty StackResourceDrifts result with the expected CloudFormation drift-detection behavior. Done means AWS::KMS::Alias appears in the drift detection results.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.