Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ResolverEndpoint fails creation because of create requestor id

See original GitHub issue

Hi, 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


  • **CLI Version : 1.16.2
  • **Framework Version: 1.16.2
  • **OS : Mac OS 10.14.6 Mojave
  • **Language : Typescript


The API documention mentions an option for CreatorRequestId

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:closed
  • Created 4 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

ccqwcommented, Apr 16, 2020

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!

AbhilashPMcommented, May 24, 2021

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

CreateResolverEndpoint - Amazon Route 53
CreatorRequestId. A unique string that identifies the request and that allows failed requests to be retried without the risk of running the operation...
Read more >
create-resolver-endpoint — AWS CLI 2.9.8 Command ...
The CreatorRequestId allows failed requests to be retried without the risk of running the operation twice. The ARN (Amazon Resource Name) for the...
Read more >
Class: AWS.Route53Resolver
Run the following AWS CLI command to create a Resolver endpoint: create-resolver-endpoint --name [endpoint_name] --direction INBOUND --creator-request-id ...
Read more >
InternalServiceErrorException when trying to create an ...
Route53 Resolver endpoint: InternalServiceErrorException: [RSLVR-00201] Internal Service Error, please retry your request. Trace ID: ...
Read more >
The OCID of the target resolver. --subnet-id [text] ¶. The OCID of a subnet. Must be part of the VCN that the resolver...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found