When specifiying `customDomain` shouldn't
`hosted...
# helpj
Jan Plaček
03/14/2022, 9:55 AMWhen specifiying
customDomainhostedZonedomain<http://foo.com|foo.com> Copy code
[Error at /dev-talsec-talsec/Web] Found zones: [] for dns:<http://portal.dev.foo.com|portal.dev.foo.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 "<http://portal.dev.foo.com|portal.dev.foo.com>" in your AWS Route 53 account. Please double check and make sure the zone exists, or pass in a different zone.t
thdxr
03/14/2022, 11:05 AMNot necessarily, if you have seperate for dev / staging etc you might have this configured differently
j
Jan Plaček
03/14/2022, 11:07 AMJan Plaček
03/14/2022, 11:07 AMSo for example, if your custom domain is set to, SST will look for a hosted zone called<http://dev.example.com|dev.example.com>. If you have it set under a different hosted zone, you’ll need to set that explicitly.<http://example.com|example.com>
Jan Plaček
03/14/2022, 11:08 AMSo, the way I understand it is, that if hosted zone is
<http://exmaple.com|exmaple.com>Jan Plaček
03/14/2022, 11:12 AMIn other words:
Copy code
customDomain: "<http://dev.api.example.com|dev.api.example.com>" Copy code
customDomain: {
domainName: "<http://dev.api.example.com|dev.api.example.com>",
hostedZone: "<http://example.com|example.com>",
},t
thdxr
03/14/2022, 1:05 PMI think the reason that's not the default behavior is usually people have a zone per environment domain
thdxr
03/14/2022, 1:07 PMI think maybe it should behave like this
customDomain: <http://dev.api.example.com|dev.api.example.com><http://api.example.com|api.example.com>j
Jan Plaček
03/14/2022, 2:13 PMOk, but the error indicates it looks for zone that equals to domain, therefore the example/guide is not correct, right?
Jan Plaček
03/14/2022, 2:15 PMI noticed in case of api gateway:
https://docs.serverless-stack.com/constructs/Api#configuring-custom-domains
it's documented bit more clearly:
Note that, normally SST will look for a hosted zone by stripping out the first part of thedomainName
Jan Plaček
03/14/2022, 2:19 PMOr perhaps the error is just a bit misleading as it tries to look for
<http://example.dev|example.dev>Jan Plaček
03/14/2022, 2:32 PMGuess I just got confused by the different behavior here...
2 Views