I m going through the guide and when deploying to prod I m g Serverless Stack #help

I'm going through the guide, and when deploying to...

Pablo Fernandez

02/10/2022, 9:17 AM

I'm going through the guide, and when deploying to prod, I'm getting this error:

Copy code

prod-ww3-api failed: The domain name you provided already exists. (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; Request ID: 04242074-0225-44bc-a8d1-a1cf94aef985; Proxy: null)

It is correct that the domain name already exists, it's handled by CDK, it has many more entries (email, and other things). The frontend didn't have a problem with the domain existing though, it just injected the records into it.

Frank

02/10/2022, 10:51 AM

Hi @Pablo Fernandez, to use a domain in your Route 53 account, you’d have to add that domain to API Gateway. SST does this for you automatically.

Frank

02/10/2022, 10:52 AM

The error suggests that you have another API Gateway project using the same domain, and the domain has already been added to API Gateway.

Pablo Fernandez

02/10/2022, 10:53 AM

Yeah, I switched it from api.example.com to api2.example.com and it worked.

Frank

02/10/2022, 10:53 AM

ah yeah

Pablo Fernandez

02/10/2022, 10:53 AM

But I'm not using api.example.com anywhere.

Pablo Fernandez

02/10/2022, 10:53 AM

Or... rather... anywhere that I can find.

Pablo Fernandez

02/10/2022, 10:54 AM

Checked API Gateways and CloudFront distributions.

Pablo Fernandez

02/10/2022, 10:54 AM

I only have this project in this AWS account plus CDK stacks that create the Route53 zones with a few records setting MX and things like that.

Pablo Fernandez

02/10/2022, 10:55 AM

I notice that it creates the CNAME for DNS verification to create the certificate for api.example.com, but it fails to create the certificate.

Pablo Fernandez

02/10/2022, 10:55 AM

Or rather, there's no certificate.

Frank

02/10/2022, 10:55 AM

If you go into ur API Gateway console > select

Custom domain names

on the left, what does it show?

Pablo Fernandez

02/10/2022, 10:56 AM

(I just deleted the api stack that created api2.example.com)

Frank

02/10/2022, 10:57 AM

I see. Can you try using

<http://api.example.com|api.example.com>

again? That should work now 🤔

Pablo Fernandez

02/10/2022, 10:58 AM

Give me a sec while I run deploy.

Pablo Fernandez

02/10/2022, 11:12 AM

Got the error again:

Copy code

prod-ww3-api | UPDATE_FAILED | AWS::ApiGatewayV2::DomainName | ApiDomainNameAC93F744 | The domain name you provided already exists. (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; Request ID: 40cf6d9f-8c05-4305-b1ae-b7046e117ac6; Proxy: null)

Jay

02/14/2022, 9:15 PM

@Frank just bringing this up again.

Pablo Fernandez

02/14/2022, 10:59 PM

I also asked in SO: https://stackoverflow.com/questions/71085161/when-deploying-my-aws-api-gateway-it-fails-with-the-domain-name-you-provided-a

Frank

02/17/2022, 9:32 PM

Hey @Pablo Fernandez, hmm maybe check switch to other regions and other AWS accounts you might have used, and see if the domain exists in the API Gateway console.

Frank

02/17/2022, 9:34 PM

If it’s not there, the only thing i can think of would be to contact AWS support and see if something is cached on their end.

Pablo Fernandez

02/19/2022, 9:05 AM

@Frank I'm putting everything in a single region exactly to avoid this sort of problem. And I use the Tag Editor to search cross-region and make sure I don't get resources on other regions.

Frank

02/22/2022, 2:50 AM

hmm.. are you able to create the domain manually in API Gateway console?

Pablo Fernandez

02/24/2022, 8:09 PM

No, I get the same error.

Pablo Fernandez

02/24/2022, 8:10 PM

Or I did, the last time I tried.

Frank

02/27/2022, 8:46 AM

I see. Yeah if you get the same error in the API Gateway console, and its not in one of your account/region, you might’ve to contact AWS support to get help.

Open in Slack

Previous Next