Migrate externally hosted website path by path to fargate

0

Hi there, we are in the process of evaluation of how to migrate a web project from an external web hosting service to AWS Fargate. We would prefer to migrate certain pathes first and then move along with more paths as soon as the implementation on the Fargate Service is ready.

E.g.: www.my-website.com/already-migrated-path (served from AWS Fargate) www.my-website.com/not-yet-migrated (served from previous web hosting service)

Are there any best practices or ideas how to do this?

Kind regards, Nils

4 Answers
0

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.

profile picture
EXPERT
answered a month ago
0

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

Nischu
answered a month ago
0

... or with CloudFront?

Nischu
answered a month ago
0

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)

Nischu
answered a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions