Migrate externally hosted website path by path to fargate

The only way I can see you doing this is to have a reverse proxy in-front of your website such as ngnix.

Host this as a container in fargate and use path rules to send the request either to your new website or your old one. You need to have your old website accessible on a different host url for this to work.

Is that something that could also be accomplished with path routing of an alb (in order not to manage an nginx)?

... or with CloudFront?

If anyone else is looking for something like this. I found this article which gave me three options to accomplish what I was looking for: https://aws.amazon.com/de/blogs/architecture/serving-content-using-fully-managed-reverse-proxy-architecture/

(Thanks @Gary Mclean - the keyword "reverse proxy" helped me to finally find this resource)