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

AWS::EC2::VPCPeeringConnection DNS Resolution

Open
#169 22 comments 142 reactions 0 assignees View on GitHub
networking & content deliv
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

## Instructions for CloudFormation Coverage New Issues Template

Quick Sample Summary:
1. Title -> AWS::Service::Resource-Attribute-Existing Attribute
2. Scope of request -> AWS::EC2::VPCPeeringConnection ist missing DNS Resolution Feature for Accepter and Requester
3. Expected behavior -> There should be an option to enable/disable dns resolution for accepter and for requester

As you can see in the Link https://docs.aws.amazon.com/de_de/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-vpcpeeringconnection.html
there is a missing feature to enable Requester and Accepter DNS Resolution.
You can do it with the AWS Console.
And also with the CLI: https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-vpc-peering-connection-options.html

It would be nice to see that feature in Cloudformation

Contributor guide

Open the contributing guide

Research direction

Start by reading the AWS CloudFormation VPCPeeringConnection resource documentation and the linked EC2 modify-vpc-peering-connection-options CLI reference. Confirm the missing requester and accepter DNS-resolution options and determine how CloudFormation should expose them. Done means the resource supports enabling or disabling both options with documented behavior and coverage tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.