Developer Tools
RecognitionAWS Amplify
Services and tools for building and deploying web and mobile applications, including branch-based application environments.
Key points
- An Amplify branch can have its own deployed application environment.
- Environment variables and backend resources still need explicit branch/environment separation.
- Use approved artifact and configuration rather than assuming source branching alone provides isolation.
Best-known use cases
- Branch-based web application previews and integration environments.
- Managed web application build and deployment.
What candidates often confuse it with
- Amplify branch environments are deployed application surfaces; Git branches are source-history labels.
- Amplify deployment differs from API Gateway stages and Lambda aliases, though all can represent environment/version boundaries.
Key takeaway
Recognize Amplify branches as managed application environments only when deployment and configuration are actually bound to them.
Related services
- AWS CodeBuild
- AWS CodePipeline
- AWS Lambda
Relevant exam tasks
- D3.3 — Automate deployment testing
- 3.3.3 — Create application environments that use approved versions for integration testing (for example, Lambda aliases, container image tags, AWS Amplify branches, AWS Copilot environments)