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 Antworten
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
EXPERTE
beantwortet vor 3 Monaten
0

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

Nischu
beantwortet vor 3 Monaten
0

... or with CloudFront?

Nischu
beantwortet vor 3 Monaten
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
beantwortet vor 3 Monaten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen