aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
AWS::EC2::VPCEndpoint - Drift not checked / detected
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::EC2::VPCEndpoint
### Issue Description
After deploying a AWS::EC2::VPCEndpoint resource within a CloudFormation stack, then performing drift detection on the stack, the drift results do not include the AWS::EC2::VPCEndpoint resource, yet the [documentation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/resource-import-supported-resources.html?icmpid=docs_cfn_console) shows that this is a resource type which supports drift detection operations.
### Expected Behavior
Since this resource type is supported, as per the AWS docs, the drift results should include it, and also indicate whether there is drift or not.
### Observed Behavior
Drift results do not include AWS::EC2::VPCEndpoint resources, whether the resource is actually drifted or not.
### Test Cases
Deploying any AWS::EC2::VPCEndpoint resource appears to yield the same result. I used the [example template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-vpcendpoint.html#aws-resource-ec2-vpcendpoint--examples--Create_a_gateway_endpoint) in the AWS docs to test this.
Contributor guide
Research direction
Start with the AWS::EC2::VPCEndpoint documentation and its linked example template, then reproduce stack deployment and drift detection using that template. Compare the resulting drift output with the documented support for drift detection. Done means the endpoint appears in drift results and correctly reports whether it is drifted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100