To confirm Custom Domains managed by Seed is not supported f Serverless Stack #seed

To confirm: Custom Domains managed by Seed is not ...

Toby Harris

05/21/2022, 2:23 PM

To confirm: Custom Domains managed by Seed is not supported for SST projects, only Serverless Framework? (I am getting

There are no available API endpoints in your app.

in App Settings → Custom Domains, and searching here suggests that at least was the case in the past)

Frank

05/25/2022, 4:20 AM

Hey @Toby Harris, yup, you can only configure custom domain for Serverless Framework apps on Seed.

Frank

05/25/2022, 4:21 AM

It’s highly recommended to configure custom domains in your SST app (ie. in the

Api

and

StaticSite

construct).

Frank

05/25/2022, 4:25 AM

There are a couple of advantages to let SST manage the custom domain: 1. You have the flexibility to configure domains based on the current stage, ie.

Copy code

customDomain: app.stage === "prod"
  ? "<http://mydomain.com|mydomain.com>"
  : `${app.stage}.<http://mydomain.com|mydomain.com>`

2. SST is aware of the state of the configuration. On remove, SST is able to clean it up.

Frank

05/25/2022, 4:27 AM

Manually configuring domains on Seed is not ideal, but there wasn’t a better alternative way for Serverless Framework.

Frank

05/25/2022, 4:27 AM

Hope that makes sense.

Toby Harris

05/25/2022, 9:37 AM

Thanks for getting back to me. In the end I figured as much, good to have it confirmed. FWIW #1, it’s pretty clear when you follow the guide, but if you come to this some time after following the guide, it’s not clear (e.g. you search and get the Seed page, or an older guide page). FWIW #2, I submitted a GitHub issue around something I hit: API’s customDomain does not update Route53 on subsequent changes FWIW #3, I’m probably not the first person to want to add an

api

subdomain to an existing company domain with DNS etc. elsewhere. Having added Route 53 for just the subdomain, wasn’t hard to figure out I needed to specify

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

for both hosted zone and domain name, but explicitly stating that in the guide / a help page would be good.

Open in Slack

Previous Next