aws-amplify / aws-amplify/amplify-hosting
URL rewrite params
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
Hi Team,
I have a scenario where a multi-tenanted SPA app is deployed on amplify with wildcard subdomains with help of cloudfront. We generate dynamic site maps on the backend for each tenant separately for each subdomain.
I would like to achieve the following using rewrite.
app1.example.com/sitemap.xml - api.backend.com/app1.example.com/sitemap.xml
app1.example.com/robots.txt- api.backend.com/app1.example.com/robots.txt
app2.example.com/sitemap.xml - api.backend.com/app2.example.com/sitemap.xml.
app2.example.com/robots.txt- api.backend.com/app2.example.com/robots.txt
Is the host name of the request available in the rewrite rules for me to use the reverse proxy rewrite?
Contributor guide
Research direction
Start with Amplify Hosting rewrite rules and the reverse-proxy behavior described in the issue. Determine whether the incoming hostname is available to rewrite configuration, and document whether tenant-specific sitemap.xml and robots.txt mappings can be achieved for wildcard subdomains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100