Monday, May 6

AWS Amplify Console + Route 53 + Git : Almost Magic.

Amplify This!

Over the last month or so I have been playing around with AWS Amplify – I am hooked. What is this magic you ask? Well it is simple CI/CD that makes deploying a website quick and basically painless – at least if you are creating a static simple HTML site. We get a little more complexity when we add the back end, but even then it is pretty much magic in a box.

What do you need? An AWS Account, a Github account, a domain that is registered on AWS Route 53 and some basic HTML knowledge.

Setting up a quick Git Repository.

  • Log into your github account – https://github.com/login
  • Click on the “New” repository button
  • Type in a name, you can set it public or private, initialize it how you like.
  • Clone to your local machine, open up the directory.
  • Go into your local copy and create an HTML page using your favorite editor save it as index.html.
  • Push the new file to your repository

Setting up AWS Amplify

  • Log into your AWS account
  • Under Services find AWS Amplify
  • Select Amplify Console
  • Click on “Connect app”
  • Select GitHub then click “Continue”
  • you will be prompted to sign into GitHUb
  • Select your repository, leave the branch as “master” and click Next, then Next again, then click “Save and deploy”
  • Now you wait for a few minutes while the magic happens. You will seen the screen update a few times and finally you will be able to click on your link and “ta-da” your new page is up and running.

Here is where the real fun starts. Make a change to your index.html file and push it to your repository. You can actually watch AWS Amplify pick up the change and push your new files live.

Link in your Domain Name

  • In AWS Amplify select your app
  • Under App Setting select “Domain Management”
  • Click on “Add domain”
  • Select your domain from the drop down list then click “Configure domain”
  • Click save and wait while the DNS magic happens
  • Your SSL will be created for you (no pesky http vrs https problems)