hey guys, using a custom domain and having some issues. // Create the API this.api = new sst.Api(this, "Api", { customDomain: scope.stage === "prod" ? "example.com" : undefined, ... // Show the API endpoint in the output this.addOutputs({ ApiEndpoint: this.api.customDomainUrl || this.api.url, }); I can see the hosted zone in route 53 and it looks fine, but i get this error running npx sst deploy --stage prod [Error at /prod-Example-api/Api] Found zones: [] for dns:com, privateZone:undefined, vpcId:undefined, but wanted exactly 1 zone Found errors It seems you are configuring custom domains for you URL. And SST is not able to find the hosted zone "com" in your AWS Route 53 account. Please double check and make sure the zone exists, or pass in a different zone. Any ideas? 🙂

Should work like this, I have the same setup and it works. There is probably an issue with your hosted zone setup in AWS, maybe check what the "Test Record" functionality spits out

this?

Just to make sure, you don't really have "example.com" in the config file, right?

haha i have my domain there 🙂

hmmm, the tool result looks fine I guess

yeah... the account has full admin so dont think its permission related

would probably be a different message

Type Public hosted zone

I have an A record for api.mydomain.com, which is also what I use in SST config

that sounds like something

the one you pasted in OP

i think i will explore the arecord and sst config you mentioned - it sounds like something

you seem to have an A record for your domain that you are also using in the SST config, so I guess it should work

how did your a record for api.mydomain.com create? does npx sst deploy --stage prod create that or do you have to do that manually the first time?

I think I did it manually

hmm

maybe delete and rewrite the line with scope.stage in your SST config, it's weird that it's trying to find the hosted zone "com" and not your actual domain...maybe there is a weird invisible character in there that breaks it

ok sure thanks

I think I didn't create it manually after all, I'm pretty sure I followed this: https://serverless-stack.com/chapters/custom-domains-in-serverless-apis.html

i think i got it

what was it?

scope.stage === "prod" ? "example.com" doesnt work it has to be like this scope.stage === "prod" ? "api.example.com" which makes sense for an api gateway

hmmm, that does sound a bit like a bug, though, like it always assumes a subdomain and then just strips the string before the dot to find the hosted zone

i remember something to do with i forget what its called but the "domain bit segments" It wouldnt make sense to deploy my API to the place of my website too though

yeah, I guess it's not very common to host an api at "example.com"

thanks alot though, it was your api.myexample that gave me the clue, i was originally following that document but got caught up in creating stages for my urls for test and dev too

haha, I know the feeling, lots of new stuff to do, can easily get lost

instead of api.my.com and dev.api.my.com and test.api.my.com

if test.api.my.com doesn't work, you could try test-api.my.com or something

will do. now i just need to figure out how i point my frontend bit to my.com 😄

you make a FrontendStack and use sst.ReactStaticSite for example

yeah followed that, but its how you point that to your .com

Not sure how you do it with other frameworks, there might be other sst. constructs for that

i think it might be the customDomain bit again but in the frontend stack. lets see fingers crossed 🙂

ah, yeah, that is here: https://serverless-stack.com/chapters/custom-domains-for-react-apps-on-aws.html

ah nice one

@Kristian Lake @Adrian Schweizer hey guys thanks for digging into this one. I just tried it on my end, and I can confirm the hosted zone look up is a bug.

thanks Frank

Let me follow up on the

AWS::CloudFront::Distribution

issue in the thread below.