Our serverless API uses API Gateway and it gives us some auto-generated endpoints. We would like to configure them to use a scheme like api.my-domain.com or something similar. This can take a few different steps through the AWS Console, but it is pretty straightforward to configure through Seed.

Head over to our app settings.

Seed app pipeline screenshot

Here click on Edit Custom Domains.

Click Edit Custom Domains in app settings screenshot

And click Add for our production endpoint.

Click Add for production endpoint in custom domain settings

Seed will pull up any domains you have configured in Route 53. If you want to purchase a domain in Route 53, we have an extra credit chapter to help you. You can also migrate any existing domains to Route 53; you can read about it here.

Hit Select a domain and you should see a list of all your Route 53 domains. Select the one you intend to use. And fill in the sub-domain and base path. For example, you could use api.my-domain.com/prod; where api is the sub-domain and prod is the base path.

And hit Add Custom Domain.

Click Add Custom Domain button for prod endpoint

Seed will now go through and configure the domain for this API Gateway endpoint, create the SSL certificate and attach it to the domain. This process can take up to 40 mins.

While we wait, we can do the same for our dev endpoint. Select the domain, sub-domain, and base path. In our case we’ll use something like api.my-domain.com/dev.

Click Add Custom Domain button for dev endpoint

Hit Add Custom Domain and wait for the changes to take place.

Now that we’ve automated our deployments, let’s do a quick test to see what will happen if we make a mistake and push some faulty code to production.