Staging and PR previews

Feature work → PR previewPR preview
Temporary Amplify hosting URL created for a pull request so you can review the built site before merge. → stagingstaging
Long-lived Git branch (and Amplify branch) used as a pre-production environment before promoting to main. → main. GitHub Actions is the merge gate; AmplifyAmplify
AWS Amplify Hosting - managed CDN hosting for front-end web apps. Git-connected continuous deployment is one option; this lab uses that path for branch and PR preview URLs.
Amplify Hosting docs builds from amplify.ymlamplify.yml
Root amplify.yml file that tells Amplify how to install, build, and which artifact directory to publish. in parallel.

Close

Flow

1. Branch → PR into staging (CI green; Amplify builds a preview)
2. Merge → validate on https://staging.<app-id>.amplifyapp.com
3. PR staging → main (same CI gate — protect staging with Restrict deletions first so auto-delete head branches cannot remove it)
4. Merge → https://main.<app-id>.amplifyapp.com

Caution

Do not open feature PRs directly against main. Without deletion protection, promoting staging → main with auto-delete head branches on will delete Git staging.

Preview hosts: delete them in the Amplify Console, or enable automatic branch deletionautomatic branch deletion
Amplify setting that automatically removes a preview host when its Git branch is deleted. Same end state as deleting that Amplify branch in the Console. so Amplify removes them when the Git branch is gone. Neither deletes the Amplify app.

Next: Prerequisites.

Diagram icons from AWS Icons andArch Icons.