amplify redirect rules

Yes, it is possible to define conditions for AWS Amplify redirect rules, including conditions based on the hostname. However, the specific capability to directly condition redirects based on hostname is not explicitly supported in Amplify's standard redirect configuration.

Instead, you can achieve similar results by using a combination of techniques:

1. You can use regular expressions in your source patterns to match specific URL structures, which could include hostname patterns if your setup allows for it.

2. For more complex scenarios, you might need to implement custom server-side logic or use AWS Lambda@Edge with CloudFront to handle conditional redirects based on hostnames.

3. Amplify does support country code-based redirects, which could be useful if your hostname requirements align with geographic distinctions.

4. You can create multiple redirect rules to handle different scenarios, potentially mimicking hostname-based conditions by carefully structuring your URL patterns.

For your specific example:

{ "source": "/<>", "status": "200", "target": "/de/<>" }

This rule as written would apply to all requests. To make it more specific, you could modify the source pattern to match only certain URL structures that might imply a particular hostname or language preference.

Keep in mind that while Amplify offers powerful redirect capabilities, for very complex routing scenarios or hostname-specific logic, you might need to consider additional services or custom implementations to fully meet your requirements.

Sources
Remove default AWS Amplify domain | AWS re:Post
AWS Amplify redirect from/to custom domain | AWS re:Post
Amplify redirect with angular i18n not working correctly | AWS re:Post