aws-amplify / aws-amplify/amplify-hosting
Migrate s3 bucket to amplify and 301 redirects
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
** Please describe which feature you have a question about? **
Domains and Redirects
** Provide additional details**
Connecting our domain that is currently in use by our s3 bucket failed (which makes sense). What would be the best steps to go about migrating with minimal downtime?
However...before doing this, I want to make sure that 301 redirects are working properly. I setup a few and am viewing on the amplify generated URL (XXX/amplifyapp.com). These 301s are still ignoring redirects. I have built the site using Vue Routing, is this a conflict of routing? For the meantime, I have the routes going to their new views but would prefer to have 301 redirects.
Contributor guide
Research direction
The issue names an S3 bucket, Amplify Hosting, Domains and Redirects, and Vue Routing but no repository file or test. Start by reproducing the 301 behavior on the Amplify-generated URL and comparing it with the custom-domain migration path. Done would require a documented minimal-downtime migration and confirmed working 301 redirects, including whether Vue routing conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100