O Impacto da Implementação do CloudFront na Performance e Disponibilidade da Fusion DMS (In English)

With the growing adoption of Fusion’s SaaS platform, the company needed to address challenges related to:

• Map and model the entire technology architecture;

• Propose technical migration scenarios;

• Conduct a capacity planning and infrastructure dimensioning study;

• Optimize systems architectures;

• Performance in your application’s response time;

• Increased security through encryption in transit;

• Anti DDoS protection;

• Provide specialized support in cloud computing architecture and technology operation.

Technical enablement

Fusion DMS infrastructure is composed by different systems and subsystems. The architecture is based on Route 53 for DNS service, Cloudfront acting as CDN and also providing security – since it offers native anti DDoS – and mainly, delivery content locally in Brazil – reducing time response for their clients. Besides Route 53 and Cloudfront, Fusion implement’s an infrastructure that contains: Application Load Balancers, EC2 instances for backend systems, RDS for system’s databases, Cloudwatch for monitoring, S3 for object storage.

The fusion project was divided in three phases:

In The first step  we conducted a detailed Well Architected review. This resulted in a series of several changes to be made in the solution. The second phase of the project was dedicated to instrument the solution for a better monitoring and understanding of the software behavior. The third part was committed to improve the performance, among other solutions 10 cloudfront distributions were created.

AWS Services deployed: 

• Amazon EC2, Amazon RDS, Amazon S3, Amazon CloudWatch, Amazon EFS, Amazon GuarDuty, AWS CloudTrail, AWS Lambda, Amazon CloudFront.

Customer issues and concerns that have been overcome:

1. Operational excellence

1.1. Implementation of continuous monitoring with Amazon CloudWatch;

1.2. Integrated connectivity with high available multi zone (Multi-AZ);

2. Security

2.1. Implementation of Amazon GuardDuty for intelligent monitoring of infrastructure perimeter;

2.2. Restriction of external access to the environment, with segregation between private and public subnets for back and front end, respectively;

2.3. Access to the AWS environment for VPN-only administration;

2.4. Encryption of data at rest

2.5. Encryption of data in transit with Amazon Cloudfront.

3. Reliability

3.1. Multiple instance nodes, making it possible to balance reading and writing operations;

3.2. Minimal failover between nodes;

3.3. Using Amazon Data Lifecycle Manager to implement snapshot-level backups.

3.4. Automatic backups of the database layer;

4. Excellence in performance

4.1. Calculation of expected environment demand for rightsizing.

5. Cost optimization

5.1. The monitored environment, with a continuous flow of monitoring for rightsizing.

Third-party solutions applied:

• • Hashicorp Terraform: Infrasctructure as Code;

  • Hashicorp Vault: Secrets and key management service.

Key Results:

• • AWS managed infrastructure service;

  • Professional managed services provided;

  • 99.97% availability of the environment;

  • 23% increase in response time with Amazon Cloudfront.

Lessons learned:

• • The implementation of AWS services, allowed us to focus more on the business aspects of the project;

  • Although the planning of projects like this is important, the need for experimentation on the part of the client proved to be fundamental. In this sense, the use of AWS enables a rapid prototyping of architectures;

  • Using the AWS Well-Architected framework as a reference helps us to make clear to the customer the value of a good service partner.

Architecture Diagram: