For the subdomains we've been using so far (mlflow.thegardens.ai, api.thegardens.ai) we've been able to use AWS certificate manager to create and manage our SSL certs. But the root domain (thegardens.ai) is a special case. Route 53 can't fully import an .ai domain. We've been able at least manage our subdomains in Route 53 via NS records pointing from Namecheap to AWS. AWS Certificate Manager can't issue certs for root domains when domains are set up this way. So we need to get an SSL cert for thegardens.ai the old fashioned way.
Assumptions:
We want a static thegardens.ai site up and working for visibility purposes
Acceptance Criteria
Given I am a person interested in learning more about Garden, when I type thegardens.ai into my address bar, then I am taken to an HTTPS url and not given a warning that the site is insecure.
Circumvented this for now by using GH Pages for our SPA and pointing the root domain and www subdomain there from Namecheap. GitHub provisions the cert and HTTPS is working.
For the subdomains we've been using so far (mlflow.thegardens.ai, api.thegardens.ai) we've been able to use AWS certificate manager to create and manage our SSL certs. But the root domain (thegardens.ai) is a special case. Route 53 can't fully import an .ai domain. We've been able at least manage our subdomains in Route 53 via NS records pointing from Namecheap to AWS. AWS Certificate Manager can't issue certs for root domains when domains are set up this way. So we need to get an SSL cert for thegardens.ai the old fashioned way.
Assumptions:
Acceptance Criteria
Given I am a person interested in learning more about Garden, when I type thegardens.ai into my address bar, then I am taken to an HTTPS url and not given a warning that the site is insecure.