Setting up a hosted zone with Route53
Fuzzball needs a domain to host services like keycloak, the Fuzzball API server, and the UI. On AWS, Fuzzball needs a “hosted zone” in Route53 for a domain. It’s easy to purchase a new domain through Route53 which will automatically set up a new hosted zone. Or you can create a new hosted zone in Route53 and add a (Name Server) NS record to another domain that you or your administrator already controls.
The directions here are intended as general guidelines to give you an idea of how to proceed. They may not be up to date, and are not intended to replace AWS documentation.
Following these directions will incur cost in your AWS account.
Make sure you are logged into your AWS console, head over to the Route53 home page, and click “Get Started”.
You can select “Register a domain” and click “Get Started”.
Now come up with an idea for your new domain name, search to see if it is available, and select it if it is.
If you are ready to purchase the domain, you can proceed to the checkout where you will check pricing, provide your contact information, review, and finalize your purchase.
At this point, you will probably need to wait for some period of time for your domain to be registered and ready to use. In testing, the domain took less than an hour to become live, but your results may vary.
When your domain is live and ready to go, you will see a screen that looks like the following.
If you already have a personal domain, or you have access to a domain through your organization (and your administrators will allow you to host your Fuzzball cluster within a subdomain), you can set up a hosted zone in Route53 and then configure your DNS record to your top level domain allowing the subdomain to be delegated to Route53 from the existing domain.
This method requires you or your administrator to add NS records to your existing domain. The exact procedure differs according to your domain provider and instructions are outside of the scope of this documentation.
Make sure you are logged into your AWS console, head over to the Route53 home page, and click “Get Started”.
You can click on “Create hosted zones” and then click “Get started” again.
You will be asked to provide a domain name. This will actually be the subdomain where Fuzzball will
create the rest of the subdomains to host its various services. This value should take the form of
<mysubdomain>.<domain>.<tld>. For instance, if your organization has a domain called
groovy.org, and you want to host fuzzball there, you might enter something like
fuzzball.groovy.org.
Once you’ve created the hosted zone, you will need to gather the NS records so that you (or your
administrator) can add them to your top level domain to delegate the subdomain to Route53. You can
find those records by clicking on the Records tab and checking the box next the Record type
labeled NS. A split panel menu should open with the NS record URIs.
At this point, you or your administrator can add the NS records to the top level domain so that DNS will resolve to the Route53 hosted zone. Don’t worry if your browser complains about ssl errors when you attempt to access the subdomain. The AWS Cloud Formation process will generate certificates for your Fuzzball cluster.
Once you’ve set up a hosted zone in Route53 using one of the methods above, you will need the hosted zone name and ID to enter into the cloud formation template during the deployment step. You can find that information by clicking on your hosted zones tab and then clicking on the hosted zone name that you configured earlier. A split panel menu should open (or you can open it with the icon at the top right) containing the hosted zone name and ID to use during deployment.
Congratulations! You know have a Route53 hosted zone tied to a top level domain that you can use to deploy a Fuzzball cluster in AWS. Now you can head back to the AWS installation guide and continue with deployment.