mirror of https://github.com/docker/docs.git
Add article to TOC
This commit is contained in:
parent
3621baac04
commit
bf14764182
|
@ -3044,6 +3044,8 @@ manuals:
|
|||
title: Migration to AKS
|
||||
- path: /docker-cloud/migration/cloud-to-kube-gke/
|
||||
title: Migrate to GKE
|
||||
- path: /docker-cloud/migration/cloud-to-aws-ecs/
|
||||
title: Migrate to Amazon ECS
|
||||
- path: /docker-cloud/migration/deregister-swarms/
|
||||
title: Deregister swarms
|
||||
- path: /docker-cloud/migration/kube-primer/
|
||||
|
|
|
@ -670,9 +670,4 @@ After the migration is complete, make sure everything is working as expected. En
|
|||
|
||||
## Summary
|
||||
|
||||
In this post, we how to move an application from Docker Cloud to Amazon ECS with no code changes. While this may initially help accelerate your migration to ECS, you're still left with services like Postgres and Redis that you'll have to manage yourself. AWS gives you an opportunity to replace those services with managed services, like RDS and Elasticache which alleviate a lot of that “undifferentiated heavy lifting” we associate with managing infrastructure services like these. We encourage you to look at a migration of this kind as an opportunity to optimize by re-architecting your application to take advantage of AWS's managed services. For an in-depth look at how to do this, see [“Deploying the voting app to ECS with Fargate”](https://read.acloud.guru/deploy-the-voting-app-to-aws-ecs-with-fargate-cb75f226408f). The beauty of this approach is that lets you run containerized applciations without managing the underlying compute infrastruture, which leaves you more time to create great applications and less time worrying about your infrastructure.
|
||||
|
||||
###TODO
|
||||
1. Create a service from a task definition
|
||||
2. Explain how to register your ECS service with the AWS Service Discovery service
|
||||
3. Create an SG that allows all traffic inbound from the IPs of the NLB
|
||||
In this post, we how to move an application from Docker Cloud to Amazon ECS with no code changes. While this may initially help accelerate your migration to ECS, you're still left with services like Postgres and Redis that you'll have to manage yourself. AWS gives you an opportunity to replace those services with managed services, like RDS and Elasticache which alleviate a lot of that “undifferentiated heavy lifting” we associate with managing infrastructure services like these. We encourage you to look at a migration of this kind as an opportunity to optimize by re-architecting your application to take advantage of AWS's managed services. For an in-depth look at how to do this, see [“Deploying the voting app to ECS with Fargate”](https://read.acloud.guru/deploy-the-voting-app-to-aws-ecs-with-fargate-cb75f226408f). The beauty of this approach is that lets you run containerized applciations without managing the underlying compute infrastruture, which leaves you more time to create great applications and less time worrying about your infrastructure.
|
||||
|
|
Loading…
Reference in New Issue