ResolverEndpoint fails creation because of create requestor id
See original GitHub issueHi, I’m trying to crate an inbound resolver endpoint using the following:
new CfnResolverEndpoint(this, 'inbound-endpoint', { direction: 'INBOUND', ipAddresses: [{ ip: 'ip-address-from-my-vpc', subnetId: 'id-of-the-subnet' }], name: 'enterprise-sap-dns', securityGroupIds: [ securityGroupPreviouslyCreated ], });
Reproduction Steps
Apply cdk deploy for a app that contains one stack with the above;
Error Log
I get the following everytime I try to run it, but I get with different IDs Resolver Endpoint with creator request id d7f51869-6cd1-4705-af5c-d3e2d967eba3 already exists
Environment
- **CLI Version : 1.16.2
- **Framework Version: 1.16.2
- **OS : Mac OS 10.14.6 Mojave
- **Language : Typescript
Other
The API documention mentions an option for CreatorRequestId https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_CreateResolverEndpoint.html
But it seems that is not exposed in the CloudFormation, so it seems that its handled internally in cloudformation, is a cloud formation bug ?
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top GitHub Comments
Hopefully I can comment without reopening. I had this issue myself and discovered that the cause in my case was this:
I already had a resolver of a different type (inbound vs outbound) in my target VPC that was using the IP addresses I explicitly specified. When I explicitly specified different, unused IPs, I was able to successfully provision the endpoint.
I hope that helps someone!
Apologies for my earlier comment. One of the IPs that I was specifying was in use as a Secondary IP. I had failed to notice it before. Providing unused IP addresses solved the issue. However, I feel that the error message was a bit deceiving as it did not correctly state the cause of the error. May be if it could tell if the IP address(s) specified is already in use, then it could have been better.
Thanks to @ccqw for the pointer.