Migrate to AWS with Elastic Container Service (ECS)

Case study

8 min


Migrate to AWS with ECS: ChargeMap case study

At Technofy, we're delighted to share with you the case of ChargeMap's migration to AWS. This article outlines the challenges they faced and the solutions we proposed as a trusted partner to ensure a smooth and efficient migration to AWS.

The Challenge

ChargeMap is a fast-growing French company offering electric vehicle drivers (businesses and private individuals) services such as geolocation of charging stations and payment solution.

ChargeMap had been experiencing recurring service availability problems with their previous cloud provider, causing significant operational disruption and hampering their ability to serve their customers effectively.

As a result, they were looking for a reliable and scalable solution capable of ensuring high availability and optimal uptime for their services.

Business Pain & Challenges

The company was facing the following challenges with their former cloud provider:

Technical challenges

        1. Workload: ensure all applications run smoothly in containers
        2. Migrate data including databases, redis and Elastic Search, with minimal impact on services' uptime.

The Solution

In order to provide a reliable and scalable solution, the following steps were taken:

1. A proof-of-concept with ECS: We validated the feasibility of containerizing and deploying ChargeMap's applications on AWS using Amazon Elastic Container Service (ECS).

2. In-Depth Infrastructure and Application Study: A thorough examination led to the creation of the target architecture and a migration plan.

3. Migration to AWS (Build)

4. Migration Procedures: Comprehensive procedures were defined for each component.

5. Knowledge Transfer and Ongoing support : We accompany ChargeMap's teams throughout the migration journey to ensure an efficient transfer.

Architecture overview

Chargemap architecture

Architectural workflow:
The deployment process for ChargeMap begins with the developers tagging their code within the Git repository. This action triggers a series of automated procedures, including code compilation, archiving in ECR, and deployment within the ECS cluster.
A front-end load balancer distributes workload across cluster tasks and services, with ECS tasks able to access various AWS services like OpenSearch, Elasticache for Redis, and RDS Databases.

Organizational structure:
The AWS Organization consists of a primary / master / billing account, with additional accounts organized into teams within distinct Organizational Units.
Each environment operates on a separate account, complemented by a shared services account, to streamline resources across teams and environments.

Tech Stack

The following technologies were used in the migration to AWS:

* components already used in original infrastructure

Expected Results

The migration to AWS across ChargeMap Teams is currently in progress, and after the implementation of a highly available architecture we expect the following results :

In conclusion, the move to AWS is anticipated to empower ChargeMap, enhancing operational standards, elevating customer service, and achieving business objectives with heightened efficiency and reliability.

Thank you for reading this article. We hope you enjoyed it!

Contact us for more information about our accompaniment and expertise !