feat(docs): improve hosting with AWS Amplify document (gatsbyjs#10906)

* Added AWS Amplify Console

* Add AWS Amplify images and gifs

* Updated doc to deploying with AWS Amplify

* Update AWS Amplify doc link

* Update deploying-to-s3-cloudfront.md

* Update nav

* Added S3 docs from PR: gatsbyjs#10694 and created doc for AWS Amplify deployments

* updated docs based on PR feedback

* added amplify doc

* Reset s3/Cloudfront docs to the current docs

* Update deploying-to-aws-amplify.md

* Update deploying-to-s3-cloudfront.md

* Update deploying-to-aws-amplify.md

* Update doc-links.yaml

* Update doc-links.yaml

* Update deploying-to-aws-amplify.md

* Update doc-links.yaml

docs/docs/caching.md

@@ -33,3 +33,4 @@ How you setup your caching depends on how you host your site. We encourage peopl
 The following plugins have been created:
 
 - [gatsby-plugin-netlify](/packages/gatsby-plugin-netlify/)
+- [gatsby-plugin-s3](https://github.com/jariz/gatsby-plugin-s3)

docs/docs/deploying-and-hosting.md

@@ -5,6 +5,6 @@ overview: true
 
 Getting your shiny new Gatsby site onto the cloud is probably the first thing you will want to do now that it's built! Also, give yourself a pat on the back real quick for creating something new!
 
-In this section you'll find answers to questions about dealing with app routes that aren't at the root of your domain with `path prefixes`, as well as how to deploy to countless hosting solutions such as [Netlify](https://www.netlify.com/), [Cloudfront](https://aws.amazon.com/cloudfront/), and [GitHub Pages](https://pages.github.com/). As well as what's necessary to make sure you're fully prepared for a deploy! 🚀
+In this section you'll find answers to questions about dealing with app routes that aren't at the root of your domain with `path prefixes`, as well as how to deploy to countless hosting solutions such as [Netlify](https://www.netlify.com/), [AWS Amplify Console](https://console.amplify.aws), and [GitHub Pages](https://pages.github.com/). As well as what's necessary to make sure you're fully prepared for a deploy! 🚀
 
 [[guidelist]]

docs/docs/deploying-to-aws-amplify.md

@@ -0,0 +1,34 @@
+---
+title: Deploying to AWS Amplify
+---
+
+In this guide we'll walk through how to deploy and host your Gatsby site using the [AWS Amplify Console](https://console.amplify.aws).
+
+AWS Amplify is a combination of client library, CLI toolchain, and a Console for continuous deployment and hosting. The Amplify CLI and library allow developers to get up & running with full-stack cloud-powered applications with features like authentication, storage, serverless GraphQL or REST APIs, analytics, Lambda functions, & more. The Amplify Console provides continuous deployment and hosting for modern web apps (single page apps and static site generators). Continuous deployment allows developers to deploy updates to their web app on every code commit to their Git repository. Hosting includes features such as globally available CDNs, easy custom domain setup + HTTPS, feature branch deployments, and password protection.
+
+## Pre-requisites
+
+1. [Sign up for an AWS Account](https://portal.aws.amazon.com/billing/signup?redirect_url=https%3A%2F%2Faws.amazon.com%2Fregistration-confirmation). There are no upfront charges or any term commitments to create an AWS account and signing up gives you immediate access to the AWS Free Tier
+
+1. This guide assumes that you have setup a Gatsby project. If you need to set up a project, start with the [Gatsby Auth starter with AWS Amplify](https://github.com/dabit3/gatsby-auth-starter-aws-amplify) then come back. The starter implements a basic authentication flow for signing up signing in users as well as protected client side routing.
+
+![Gatsby Amplify](./images/amplify-gatsby-auth.gif)
+
+## Deployment
+
+1. Log in to the [AWS Amplify Console](https://console.aws.amazon.com/amplify/home) and choose Get Started under Deploy.
+   ![Gatsby Amplify2](./images/amplify-gettingstarted.png)
+
+1. Connect a branch from your GitHub, Bitbucket, GitLab, or AWS CodeCommit repository. Connecting your repository allows Amplify to deploy updates on every code commit to a branch.
+   ![Gatsby Amplify2](./images/amplify-connect-repo.gif)
+
+1. Accept the default build settings. Give the Amplify Console permission to deploy backend resources with your frontend with a service role. This allows the Console to detect changes to both your backend and frontend on every code commit and make updates. If you do not have a service role follow the prompts to create one, then come back to the console and pick it from the dropdown.
+   ![Gatsby Amplify2](./images/amplify-build-settings.gif)
+
+1. Review your changes and then choose **Save and deploy**. The Amplify Console will pull code from your repository, build changes to the backend and frontend, and deploy your build artifacts at `https://master.unique-id.amplifyapp.com`. Bonus: Screenshots of your app on different devices to find layout issues :fire:
+   ![Gatsby Amplify2](./images/amplify-gatsby-deploy.gif)
+
+## References:
+
+- [Publishing Your Next Gatsby Site to AWS With AWS Amplify](https://www.gatsbyjs.org/blog/2018-08-24-gatsby-aws-hosting/)
+- If you want more control over hosting on AWS you can also [deploy your Gatsby.js Site to AWS S3](/docs/deploying-to-s3-cloudfront/).