Configure a hub on Amazon EC2

This teaches you how to run a Gaia hub on Amazon EC2. Amazon EC2 is an affordable and convenient cloud computing provider. This example uses Amazon EC2 together with an EB3 instance for file storage.

Is this tutorial for you?

This documentation is appropriate for advanced power users who are familiar with command line tools, ssh, and basic editing configuration files.

If you are planning on running an open-membership hub or an application-specific hub, see the section on Hub Operation.

Prerequisites you need

This procedure uses Amazon AWS to choose and configure an Amazon Machine Image (AMI) running a Gaia service. For this reason, you should have an AWS account on the Amazon AWS free tier, personal account, or corporate account. These instructions assume you are using a free tier account.

These instructions assume you have already created a free domain through the freenom service. If you have another domain, you can use that instead.

Finally, setting up the SSL certificates on your EC2 instance requires you to use the terminal command line on your workstation. Make sure you have the watch command installed using the which command.

$ which watch
/usr/local/bin/watch

If watch is not located, install it on your workstation.

Task 1: Launch an EC2 instance

  1. Visit the AWS Free Tier page and choose Sign in to the Console.

  2. Make sure your region is set to one close to you.

  3. Under Build a solution choose Launch a virtual machine.

    The system opens the EC2 dashboard.

  4. Enter Blockstack Gaia in the search bar.

    The system finds AMIs in the Marketplace and the Community.

  5. Choose Community AMIs.

    The system displays the available Gaia hub images.

  6. Select the most recent version of the image.

    Each image name has this format:

    blockstack-gaia_hub-STORAGETYPE-VERSION-hvm - ami-BUILDTAG

    So, the blockstack-gaia_hub-ephemeral-0001.0.1-hvm - ami-0425cf8c91bb2d331 image uses ephemeral storage, is at version 0001.0.1 and has the 0425cf8c91bb2d331 tag.

    You can choose an image that uses ephemeral or EBS storage. The ephemeral storage is very small but free. Only choose this if you plan to test or use a personal hub. Otherwise, choose the AMI for elastic block storage (EBS).

    After you select an image, the system displays Step 2: Choose an Instance Type page.

  7. Select t2.micro and choose Next: Configure Instance Details.


    To configure instance details, do the following:

    1. Select a VPC.

      A default VPC is created with a free tier account. You can use this default VPC. Or you can choose another VPC. If you choose another VPC, ensure the Subnet value is set to a subnet reachable by a public IP.

      Important: If you're using a private subnet, you should attach an elastic IP (EIP) to the VM. This EIP allows you to reboot the instance without worrying whether the address will reset. To attach an IP, press allocate new address and follow the instructions to attach the EIP to your new EC2 instance.
    2. Set Protect against accidental termination.

      If you terminate a Gaia instance, you lose all the data associated with it. Protection adds an extra step to terminating your Gaia instance.

    3. Open the Advanced Details.

      At this point, you are going to configure environment variables for your instance.

    4. Paste the following into the Advanced Details.

      {
        "ignition": { "version": "2.2.0" },
        "storage": {
          "files": [{
            "filesystem": "root",
            "path": "/etc/environment",
            "mode": 420,
            "contents": {
              "source": "data:application/octet-stream,API_KEY%3D<KEYPHRASE>%0ADOMAIN%3D<DOMAIN_NAME_VALUE>%0ASTAGING%3D<STAGING_VALUE>"
            }
          }]
        }
      }
      
    5. Replace the following values in the JSON.

      Value Description
      <KEYPHRASE> A phrase to pass when using the hub admin. For example, hubba is a fun key phrase.
      <DOMAIN_NAME_VALUE> Your hub's domain name. For example, maryhub.ml is the domain name in this example.
      <STAGING_VALUE>

      Indicates what type of SSL to create, testing (`1`) or production (`0`). Set testing if you want to test without worrying about rate limiting. A testing cerificate is not secure.

      For this tutorial, use production (`0`).

    6. Check your Advanced Details they should look similar to the following:

        {
          "ignition": { "version": "2.2.0" },
          "storage": {
            "files": [{
              "filesystem": "root",
              "path": "/etc/environment",
              "mode": 420,
              "contents": {
                "source": "data:application/octet-stream,API_KEY%3Dhubba%0ADOMAIN%3Dmaryhub.ml%0ASTAGING%3D0"
              }
            }]
          }
        }
      

    At this point, you have configured your instance details.


  8. Choose Next: Add Storage.

    The storage is set according to the AMI you selected.

  9. Choose Next: Add tags.
  10. Add a Key of purpose with the Value gaia.

  11. Choose Next: Configure Security Group.
  12. Create a security group with the following three types:

    Type Protocol Port Range Source Description
    SSH TCP 22 My IP optional
    HTTP TCP 80 Anywhere optional
    HTTPS TCP 443 Anywhere optional
  13. Choose Review and Launch.

    The system may warn you that the selection is not free tier eligible. You can ignore this for now.

  14. Press Launch.

    The system prompts you for a key pair.

  15. Select Create a new keypair or Choose an existing key pair.
  16. Select Launch Instances.

    The system launches your instance.

During the launch process the machine starts and runs some initial setup processes. These processes take a few minutes depending on the network, typically launching does not take more than 10 minutes. While this is happening the instance Status Checks reflect the Initializing status.

Task 2: Test your Gaia server

Now, you are ready to test your Gaia server and make sure it is up and running.

  1. Visit the AWS Free Tier page and choose Sign in to the Console.

  2. Choose All services > EC2.

    The system displays the EC2 Dashboard.

  3. Select Running Instances.

    The system displays your running instances.

  4. Locate your recently launched Gaia server.

    Make sure the instance shows as running and Status Checks are complete. Completed status checks ensures the Gaia processes and service were started.

  5. Select the Description tab.

  6. Locate the IPv4 Public IP value.
  7. Copy the IP and paste it in your browser.

    You should see a message that your connection is not private.

  8. Press Advanced.

    Hub test

  9. Choose to proceed.
  10. Extend the IP with the PUBLIC_IP/hub_info tag like so.

    You should see a response from your Gaia hub!

    Hub test

    At this point, you should see a Not secure message in the browser. That’s because you haven’t yet enabled SSL certification. While HTTPS is not required simple to run the hub services, Blockstack will only connect to a hub and write to its storage over a valid HTTPS connection.

Task 3: Configure a domain name

At this point, you can point a domain to your Gaia hub. Although it’s not required, it is highly recommended. If you use a domain, you can migrate your instance to a different server (or even provider such as Azure or Dropbox) at any time, and still access it through the domain URL. Just point your domain at the IP address for your EC2 instance. Use an A Record DNS type.

These instructions assume you have already created a free domain through the freenom service. To point this freenom domain to your Gaia hub, do the following:

  1. Log into your freenom account.
  2. Choose the Manage Freenom Domain tab.
  3. Add an A record leave the Name field blank.

    This points your entire domain to the hub IP.

  4. Save your changes.

  5. Create a CNAME record.

    For example, you can use the prefix www with your domain name. When you are done, your

  6. Save your changes.

    At this point, your DNS management should look similar to the following except that with your domain rather than the maryhub.ga domain.

    DNS fields

  7. After your changes propagate, visit your new domain at the hub_info page.

    Domain test

    If you receive another Your connection is not private dialogs, take the option to proceed to your domain. The Not secure message should no longer appear in the browser bar. If the message does appear, try waiting a few minutes for your recent changes to propagate across the net domain servers. Then, refresh the page.

  8. Check the SSL certificate for your hub.

    Each browser has its own check procedure, for example, Chrome:

At this point, you have the following. An EC2 instance running Gaia and a DNS record pointing your domain to this instance.

AWS hub tips and tricks

Once your Gaia storage hub is up and running on AWS, you may occassionally need to troubleshoot. This section contains some useful information for interacting with your EC2 instance.

SSH into the Host

To SSH to the EC2 host directly:

ssh -t -i <your keyfile.pem> core@<public ip address>

Displaying the docker services

Your EC2 instance is running several docker services that support the Gaia hub. You can list these services using the docker ps command.

$ docker ps --format "table {{.ID}}\t{{.Command}}\t{{.Names}}"
CONTAINER ID        COMMAND                  NAMES
b371234dc741        "/bin/sh -c 'trap ex…"   docker_certbot_1
597866815f42        "/bin/sh -c 'envsubs…"   docker_nginx_1
1d559bc51699        "npm run start"          docker_admin_1
46d410a1dce5        "npm run start"          docker_reader_1
f83fb8d044f5        "npm run start"          docker_hub_1

Each service plays a particular role in running your Gaia hub.

Service Description
certbot Service running Let's Encrypt `certbot` client to support SSL. Certbot renews your certificates and reloads Nginx to pick up the changes.
nginx Runs an Nginx proxy in front of the reader side-car. This service does things like rate-limiting and SSL termination. Your that nginx service relies on your hub's readURL to make requests. Changes to a hub's readURL must be reflected in the nginx service configuration.
admin A simple administrative service that allows you to administer the Gaia hub. Use REST calls with this service to get and set hub configuration values.
reader The Gaia read side-car services get file requests on URLs that start with your Gaia hub's readURL. You can determine your Gaia hub's read URL by either looking for the readURL key in your Gaia hub's config file. This value is or by looking for the read_url_prefix field in the data returned by a HUB_URL/hub_info page on your Gaia hub.
hub The Gaia hub service.

Locations of key files

File or Directory Description
/etc/systemd/system Contains services for managing your Gaia hub.
/etc/environment Contains the DOMAIN and STAGING variables you entered when creating your EC2 instance.
reset-ssl-certs.service Restarts all the Gaia hub services.
/gaia/docker/admin-config Configuration for the hub admin service.

You can cat the various services to see what settings they are using.

$ cat /etc/systemd/system/reset-ssl-certs.service
[Unit]
Description=Reset Gaia to first boot

[Service]
Type=oneshot
RemainAfterExit=no
EnvironmentFile=/gaia/docker/.env
EnvironmentFile=/etc/environment
ExecStart=/bin/bash -x /gaia/docker/nginx/certbot/reset-certs.sh

[Install]

Restart services and reload certificates

This procedures requires you to interact from a workstation command line with your running EC2 instance.

  1. Open a terminal on your local workstation.
  2. Confirm the hub DNS is set correctly with the following command:

    watch -n 2 -t -g -x host <domain>
    

    Substitute your domain name for the <domain> variable. For example:

    watch -n 2 -t -g -x host maryhub.ga
    maryhub.ml has address 34.219.71.143
    

    If the command returns the correct IP, the same as appears on your EC2 dashboard, stop the process with a CTRL-C on your keyboard.

  3. Change the permissions on your downloaded .pem file.

    For example, this

    chmod 400 <location-of-pem>
    
  4. SSH from your workstation and restart it.

    This process requires that you know the location of the .pem file you downloaded when you created the keypair.

    ssh -t -i <your keyfile.pem> -A core@<public ip address> "sudo systemctl restart reset-ssl-certs.service"
    

    For example:

    $ ssh -t -i /Users/manthony/gaia.pem -A core@34.219.71.143 "sudo systemctl restart reset-ssl-certs.service"
    Connection to 34.219.71.143 closed.