We are bringing the best of Tectonic to Red Hat OpenShift to build the most secure, hybrid Kubernetes application platform.
You’re well on your way to getting up and running with CoreOS Tectonic. Let’s get started.
In this tutorial you will:
To create your AWS account:
After successfully creating the account, sign in to the AWS console.
Route 53 is an Amazon service that allows you to perform DNS management, traffic management, availability monitoring and domain registration. DNS management is the only feature of Route 53 required to install Tectonic.
When creating an AWS Route 53 Hosted Zone, enter a domain that you own and can manage.
The Tectonic installation requires a hosted zone domain in which it will create two subdomains; one for the Tectonic console, and one for the Kubernetes API server. This allows Tectonic to access and use the listed domain.
Enter the domain and click Create.
AWS provides 4 DNS nameservers for the new zone. The domain or sub-domain must be configured to use these nameservers. Visit the domain registrar to add the Route53 NS records.
Please note that it may take anywhere from minutes to hours for the changes to take effect.
To verify which nameservers are associated with your domain, use a tool like Dig or nslookup. If no nameservers are returned when you look up your domain, changes may still be pending. Here's an example command:
$ dig -t ns [example.com]
You will know the nameservers were set up correctly when the lookup yields the four provided by AWS.
Next, create an EC2 SSH key pair.
Both an Access key and an EC2 SSH key pair are required for Tectonic installation.
Before creating the key pair, make sure you are in the correct EC2 region. You can confirm your current region by clicking on the location next to your profile.
Next, configure an SSH key pair from the AWS console.
Your private key will download automatically, and your key pair name and fingerprint will be listed in the page. Make a note of the Key pair name.
Confirm that RW permissions are correctly set on your .prm file. Running ls -l
for the file should return rw-------
. Permissions should be read and write (rw) for owner, and none (—) for all other users.
Finally, create an AWS access key.
To use Tectonic with AWS, you must supply Tectonic with a set of security credentials that allow it to authenticate against your AWS account. Use the AWS console to create these credentials.
Create a new Access key ID and Secret access key pair from the AWS console.
Both the Access Key ID and its corresponding Secret Access Key are used during the Tectonic installation process.