Skip to content

Latest commit

 

History

History
53 lines (37 loc) · 1.61 KB

working-with-domains.md

File metadata and controls

53 lines (37 loc) · 1.61 KB
Raw

Working with Custom Domains

For each stage created by Hover, a CloudFront distribution is created and assigned a unique domain, which can be used to test the application. It looks like this:

d1ascr3e2rsbz3.cloudfront.net

To access the app using your own domain, Hover utilizes CloudFront aliases. To get started, you need to issue a certificate for the domain from AWS certificate manager. This certificate must be issued in us-east-1.

Once the certificate is issued, update the stage manifest file to instruct Hover to map the domain to the stage by providing two attributes under the http key: domains and certificate.

http:
  memory: 256
  // ...
  domains: domain.com
  certificate: arn:aws:acm:us-east-1:<account>:certificate/<id>

For the changes to take effect, you need to build and deploy the stage:

hover build <stage_name>
hover deploy

After a successful deployment, Hover will print a CDN Domain.

Build ID   | 39da937d-1258-4ebe-b0e4-fb92ed45135d
Stage      | clouder-dev
CDN Domain | d1ascr3e2rsbz3.cloudfront.net

Use this domain as a value for a CNAME record in your domain's DNS settings.

TYPE NAME CONTENT
CNAME domain.com d1ascr3e2rsbz3.cloudfront.net
CNAME * d1ascr3e2rsbz3.cloudfront.net
CNAME sub.domain.com d1ascr3e2rsbz3.cloudfront.net

Using Multiple Domains

To use multiple domains, separate between them using a comma inside the domains attribute.

domains: domain.com, *.domain.com

Warning: Make sure the certificate covers all the domain names used.