4 AWS Cloud Networking Performance Optimisation Tips - Part 2

 

Hi all, this is Part 2 of the blog I posted last week, where we mentioned: EC2 Placement Groups, AWS Direct Connect and AWS Load Balancers. 

These tips are relevant to the many clients that already have a significant portion of their applications in AWS or if you are currently architecting an application to run in AWS.

These tips will give you some great options as to some of the best ways to design and consume your AWS services to either solve current performance issues or to implement in the most optimal fashion. 

Here are 3 more AWS services that are specially designed to solve performance issues:

#1 AWS route 53

Route 53 is AWS’s global DNS solution that acts like a Global Load Balancer.

It has a 100% uptime SLA. How it works is that it has access to information about your AWS environments that it can use to automatically route traffic for you across your AWS estate.

If you have an application that spans different AWS regions, Route 53 will load balance performance, based on where client access requests are coming from.

If a region goes down, it will re-route your traffic for you. It does it via the initial DNS request. You can even use Route 53 as a Global Load Balancer solution without using any other AWS services!

#2 AWS CloudFront

AWS CloudFront is AWS’s Content Delivery Network (CDN)solution.

It is easy to set up and use.

You first need to configure your content to support caching.

Then getting information onto CloudFront is easy and will exponentially improve access speeds for global users. 

#3 AWS EBS optimised block storage

There are 2 classes (and many sub types) of storage you can have on your EC2 instances:

  1. Local storage-which is ephemeral and if you kill your EC2 instance you lose your data. So be careful. 
  2. EBS persistent storage-which is block storage that you attach to an instance and is persistent data on a disk.  As the disk is not physically attached to the hypervisor it's all network based. 

Therefore, storage and network traffic use the same bandwidth which can cause contention. There they created EBS optimised instances which has dedicated throughput just for storage. It doesn't cost much extra and most of the new instances have it.

#4 S3 data transfer acceleration

This is when you need to accelerate the ingestion of data into S3. For example, for backups and archiving, S3 Data acceleration gets you onto the AWS backbone as quickly as possible.

This uses the closest AWS CloudFront point of presence to accelerate upload of data via compression and other optimisation features.

A note of caution. It is still imperative to test your applications with these features first and ensure it works for your use case as stated. 

If you are interested in our other Cloud, Infrastructure and Security related Blogs please click here.

Need to Optimise Your Storage Requirements?