aws-amplify / aws-amplify/amplify-studio
⚠️ Amplify Gen 1 & Amplify Studio are in Maintenance Mode ⚠️
- Dominant language
- No language data
- Stars
- 135
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
> [!IMPORTANT]
> **Amplify Gen 1 is in maintenance mode.** Amplify Studio builds on Gen 1 and follows the same timeline.
Starting **May 1, 2026**, Gen 1 backends will receive **only critical bug fixes and security patches**, and Gen 1 will reach **end of life on May 1, 2027**.
- Existing apps continue to function — there is no forced shutdown.
- This repository no longer accepts new feature requests.
- We recommend migrating to **Amplify Gen 2** to keep receiving new features and support.
**Migration guide:** https://docs.amplify.aws/react/start/migrate-to-gen2/
**Official announcement (source of truth):** https://github.com/aws-amplify/amplify-cli/issues/14881
Please direct questions about the timeline to the announcement thread above.
Contributor guide
Research direction
This issue is an announcement rather than a code task, and it names no repository files or tests to change. Read the linked migration guide and official announcement first; the documented outcome is communicating the Gen 1 and Amplify Studio maintenance timeline and directing questions to the announcement thread.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100