AWS Amplify Console

Wondering if any of you guys have played around with the AWS Amplify Console? I just found out about it.

Quoted from the announcement:

The AWS Amplify Console is a continuous deployment and hosting service for modern web applications with serverless backends. Modern web applications include single page app frameworks like React, Angular, and Vue, and static-site generators like Jekyll, Hugo, and Gatsby.

The AWS Amplify Console accelerates your application release cycle, by deploying changes to your frontend and backend on every code commit. On connecting a Git repository, Amplify automatically determines the build settings for both the frontend framework and any serverless backend resources configured with the Amplify CLI. The app is built and deployed to a globally available content delivery network (CDN) hosted on an domain.

The Amplify Console simplifies production and development workflows by creating new frontend and backend environments every time a developer connects a new feature branch. Feature branch deployments can be password protected to restrict access to internal stakeholders during development. When it’s time to take the web app to production, simply pick your Amazon Route53 custom domain, and Amplify automatically updates the associated DNS records and generates a free HTTPS certificate.

To get started, visit

also found :

@r0berts I haven’t tested it myself, but AWS Amplify Console reports to have:

Password protection

Share yet-to-be released features with internal stakeholders by setting a username and password.


It was merged. Host on AWS Amplify | Hugo

@zwbetz highly recommended, especially compared with doing it the old way on AWS stack.

AWS Amplify Console feels like Amazon’s free answer to a Netflify / Heroku style Dockerized one button git-push workflow.

In my Hugo site I version the markdown content but not the generated public files, and Amplify Console builds everything rapidly. It’s about 5x easier than manually hosting on AWS: they handle all the S3 setup, Route53 setup, Cloudfront CDN / SSL setup for you automatically.

I use a lightly customized version of the amplify.yml build file to install the latest Hugo, since at the time of writing this Amazon’s version wasn’t current. This is my config:


1 Like

Thanks for the info. Was helping a fella the other day with the same thing, re: specifying hugo version on amplify.

Thinking about this some more, may be better to put those commands in a bash script, then call it from your amplify.yml, that way the hugo version only needs to be written once.

That, but also: there’s already an AWS-defined VERSION_HUGO env var in the Dockerfile that downloads and installs a programmatically-defined Hugo version, I just couldn’t find out how to override it. If that variable can be set, then the whole amplify.yml / bash step could be short-circuited.

1 Like