amplify-hosting VS goldstack

Amplify Web Hosting

Head to AWS Amplify Hosting and click on the Host your web app button. You’ll be redirected to this page.

Just looked up the feature request and looks like they still don’t support it https://github.com/aws-amplify/amplify-hosting/issues/56

As of today, Amplify doesn't support Next.JS@12 fully and because of that, it'd be better and safer to downgrade to version 11 (of course we'd miss some of the awesome features from v12 but that's fine). So I'm making it "next": "11.1.4" in the package.json. Since we're downgrading it to v11, we need to downgrade usage of webpack from 5 to 4 and for doing that we need to add webpack5: false to our next.config.js file. I also add SVG support to that file for the future and it looks like this:

The Bearcam Companion application was pretty much ready to go after my last post on Lambdas. The final step (at least for a minimum viable product) was to publish the site. Not surprisingly, I chose to use AWS Amplify Hosting.

Hosting a simple static website is one of those things one would expect to be easier on AWS (it is by far from the only one). AWS seem to have recognised this and now offer the AWS Amplify Hosting service. I have not used this service myself but like other services branded under the Amplify umbrella it will come with the usual trade-off: a quicker setup for less flexibility.

I've run into a similar issue where the company wanted to bring on their Wordpress blog content on one site into their main site. NextJS combined with WPGraphQL did the trick. If you are going the static site generation route the main drawback is having to rebuild and deploy every time a new blog post is made. Could host it on AWS Amplify but I use Netlify and Cloudflare Pages. Take a look through their pricing models and pick whatever feels comfortable for you (still assuming a static site generated setup). In my opinion, NextJS is good enough. If it gets the job done in a reasonable amount of time, pick it. You mention having experience with Vue so maybe Nuxt is a better option?

Amplify Web Hosting

In short: you don't. Or you enlist the help of AWS Support (which you will have to pay for). The Amplify web console doesn't share detailed build logs, so you'll have to fix your problems by trial and error.

If you're referring to Amazon's static site hosting service, Amplify, which does this kind of proxying, you'd be right that it is a PIA, however, it is also the only static site hosting service that requires you to update your routes through their console. And one of the oldest and most popular issues logged on their git repo is to have this changed.

If you have any question or comments, please reach out or raise an issue 🤗.

Thus, I started the process of developing a server-side rendering friendly template a few months ago. I released this template a while ago and have since also completed the implementation of the new version of my blog. This post contains my experiences and learnings from this process.

For any suggestions, ideas and comments, please be welcome to head to GitHub and create an issue 🤗.

The above template and boilerplate are regularly updated and automatically tested (project install & standing up infrastructure). If you nonetheless encounter any problems, please raise an issue on GitHub.

Consider helping out making this template better for others by raising an issue in GitHub if you encounter any problems or have questions or ideas.

The above assumes that there is a local .aws/config and/or .aws/credentials file present. Note that the AWS credentials in awsUser can be initialised in many different ways, see the file awsUserUtils.ts for reference or the AWS documentation on Setting SDK Credentials in Node.js.

If you have any comments or ideas for this template, please head over to the Goldstack GitHub project and raise an issue.

I originally developed a boilerplate template for Next.js with Bootstrap using Terraform version 0.12 and that has been working well for over a year now (see my original blog post). However, recently AWS announced that changes to their API would require an update of the AWS Terraform Provider. While there is an option to patch an older version of the Terraform provider, I figured that may be as good an excuse as any to update the template to the latest version of Terraform, which is 1.1 as of this writing.

Since creating and maintaining these route definitions can be quite cumbersome, I have developed a small utility that scans a folder (src/routes) for .ts files and ensures that Terraform creates routes for all handlers defined in these folders. Find the source code for this utility in collectLambdasFromFiles.ts. For information on the rules used to map file names to routes in the API, please see Defining Routes.

echo.ts: Returning a custom object.