I recently added VPC Endpoints to my CloudFormation stack. I then deleted my stack and tried to recreate it.
When I tried to recreate it, I got the following error:
private-dns-enabled cannot be set because there is already a conflicting DNS domain for secretsmanager.us-east-2.amazonaws.com in the VPC vpc-63170e0b (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameter; Request ID: b7d28d81-c2c0-4f44-9642-f22171cf513d)
I suspect the error is here because the VPC's private DNS still has an entry from the last time the stack was created.
Is there a way to manually remove entries from the private DNS of the VPC?
It's located at the address 169.254. 169.253 (and the reserved IP address at the base of the VPC IPv4 network range, plus two) and fd00:ec2::253. For example, the Amazon DNS Server on a 10.0. 0.0/16 network is located at 10.0.
Domain Name System (DNS) is a standard by which names used on the internet are resolved to their corresponding IP addresses. A DNS hostname uniquely names a computer and consists of a host name and a domain name. DNS servers resolve DNS hostnames to their corresponding IP addresses.
I received a similar error when trying to rename and VPC endpoint in a CloudFormation stack.
There is no option to wait, so I fixed it by using the following steps:
VPC
-> Vitual Private Cloud
-> Endpoints
Actions
-> Delete Endpoint
I then reran my CloudFormation stack and all worked.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With