Rewrites and redirects per environment

[watilde]

Is your feature request related to a problem? Please describe. As a developer, I want to test redirection rules for only dev environment so that I do not affect production environment.

Describe the solution you'd like Having an option "environment" to rewrite and redirects.

Alternative solutions 1) Having an environment variable 2) Set environment query string with https://github.com/aws-amplify/amplify-console/issues/97#issuecomment-906172145

Additional context A user wants to build an app on ECS on the same domain with the other app on ECS. They are considering to design Multi Origin with CloudFront, but it'd be easier if Rewrites and redirects can connect to an endpoint of ALB. In addition, their Amplify app has dev, prod environment and using environment variable to set into target address would unblock the challenge.

[swaminator]

This is currently not possible. As a workaround, you can create two apps within Amplify console - Prod and Dev. Your Prod app will only have your production branch, and your dev app can contain all your staging and feature branches.

[wgins]

+1 to this

[m1stermanager]

this would be a great feature. as long as two amplify apps vs one w/ two envs doesn't impact my cost, its a very reasonable workaround

[kumada15]

We need this feature.

[parkournick2]

+1 to this

[richbnaks7]

+1 to this

[Etep15]

Agreed. +1 to this.

[codingloop]

+1 to this

[codingloop]

Use case:

• Amplify is used to host next-JS SSR apps
• REST API's are served through different servers

Have dev environment, say using the domain abc.dev the clients to set their own subdomain, so the clients will be using the URL's like below:

• dan.abc.dev
• codingloop.abc.dev

A REST call would be like this https://dan.abc.dev/api/some-url and it needs to be redirected to server (ex: https://my-dev-app.elasticbeanstalk.com)

Now, these redirections should be based on the environment. Ex:

• (Dev environment) https://dan.abc.dev/api/some-url => https://my-dev-app.elasticbeanstalk.com
• (Prod environment) https://dan.abc.prod/api/some-url => https://my-prod-app.elasticbeanstalk.com

Due to corporate firewall policies, if the REST calls are made directly to https://my-prod-app.elasticbeanstalk.com from next.js app - they are blocked by CORS policy

[shemekhe]

+1

[jimlundblad]

+1 similar but different use case to @codingloop where we need to redirect different env domains to specific DAM urls

[justincbeck]

+100 to this. This seems like a no-brainer.