I’m looking for help designing the architecture for a website migration to a headless platform.

I’m migrating from a monolithic Drupal architecture to a headless CMS. As part of this migration, the redirects stored in Drupal need to be moved elsewhere.

Since it’s a content-heavy website, I’m taking a staged approach to releasing sections one at a time.

Here is the current plan:

1. A user requests a page, e.g. /test-page.
2. CloudFront with Lambda@Edge is used to first check for an Optimizely feature flag.
3. If the flag is “on” and the URI exists in a list of page URIs for that section, the user is forwarded to the new website.
4. Otherwise, the user continues their journey to Drupal.

The new proposed architecture, including handling redirects, is as follows:

1. CloudFront’s default (*) behavior is used to funnel all traffic.
2. A user requests a page, e.g. /test-page.
3. A CloudFront function checks if the URI is in the redirects list and handles it accordingly.
4. If not redirected, the request continues to the Lambda@Edge function as described above.

My concerns with this approach are that heavy traffic loads could be problematic for the new setup, or that I might be overlooking a simpler solution.

Any advice or suggestions would be greatly appreciated.