Added Amplify SSR deployment instructions

[Zev18]

Description (required)

This pr adds instructions for deploying a project to Amplify as an SSR app. Instructions are based on AWS's own guide.

I'm pretty sure Amplify has changed, and the listed method for deploying a static site no longer works. I have tried it myself to no avail. I'm leaving it here in case anyone can prove me wrong, but if not then I think it should be deleted.

I've also added a link to Amazon's troubleshooting page for SSR deployments (I found this useful during my deployment), and marked AWS as compatible with SSR in the deploy guides navigation component.

Related issues & labels (optional)

• Closes AWS deployment docs are incorrect/outdated #11541
• Suggested label: improve existing documentation

Discord username: zev_ro

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	81eb27a
🔍 Latest deploy log	https://app.netlify.com/sites/astro-docs-2/deploys/68116012e8b8390008c1efae
😎 Deploy Preview	https://deploy-preview-11551--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
en/guides/deploy/aws.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[astrobot-houston]

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉

Here’s what will happen next:

1. Our GitHub bots will run to check your changes.
   If they spot any broken links you will see some error messages on this PR.
   Don’t hesitate to ask any questions if you’re not sure what these mean!

2. In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳.

3. One or more of our maintainers will take a look and may ask you to make changes.
   We try to be responsive, but don’t worry if this takes a few days.

[sarah11918]

Without actually testing the steps themselves, this looks great @Zev18 ! It's really nicely written and matches the Astro Docs style.

I made two tiny suggestions. I think we can do away with the extra real estate of the note by just describing the non-official adapter in the sentence text. See what you think, and whether you think this is adequate to let people know it's not officially supported.

If anyone actually runs through the steps and confirms, please leave a review! I am reviewing based on the guide material only!

[sarah11918]

What is the title of this file? And where is this file located?

e.g. The GitHub Action for the GitHub pages deploy guide describes where to create this file like this:

It might be helpful to have similar guidance here.

You can add a title with the following Expressive Code syntax by providing a title:

```yaml title="whatever.yml"

[Zev18]

Ah, this is the build settings yaml that lives in the amplify console. It's not part of the astro project, though it can be overwritten with an amplify.yaml in the root dir iirc. I followed the existing Amplify docs' decision and didn't include a file name. Should I still title the file?