New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS::EC2::VPCPeeringConnection DNS Resolution #169
Comments
+1 |
1 similar comment
+1 |
@fwippe, @mirajranpura If you use the 👍 reaction under the main issue text, your vote will actually be counted. If you want to keep updated on this issue (to see new comments like yours or when it gets into a different state), you can use the "Notifications" settings in the sidebar on the right. |
Any progress on this? It's been almost two years. |
Comin up on 2022 real fast here - what's the latest? As of Sept 2, 2021 this is the best option I've found: https://stackoverflow.com/questions/65213615/cdk-to-enable-dns-resolution-for-vpcpeering |
+1 |
+1 (no wonder Terraform is top-dog when options like this aren't available in the first-party tooling!) |
+1 |
1 similar comment
+1 |
+1 |
1 similar comment
+1 |
Any movement? |
+1 Surely it gets added anyday now... |
Instructions for CloudFormation Coverage New Issues Template
Quick Sample Summary:
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
The text was updated successfully, but these errors were encountered: