Speed Up AWS Implementation with the Five Enterprise Cloud Design Patterns

May 15, 2020

How to deal with AWS' 212 services to quickly design Enterprise Cloud architectures that make clients happy? That's a question AWS Solution Architects have been increasingly asking. How to ensure performance efficiency? What's performance efficiency? How to guarantee system reliability? What's the best approach to provide effective security mechanisms? How to optimize costs?

 

Based on my experience advising AWS solution architects my answer is: Cloud Architecture Design Patterns; they explicitly capture expert knowledge and design tradeoffs and make this expertise widely available. By providing a vision and a logic they inspire solutions.

 

In this article, I share with you five key AWS patterns I designed to not only make solution architect jobs easy but also help clients derive the maximum value from their AWS investments.

 

The AWS Enterprise Cloud, The Five Architecture Design Patterns

 

Let's start by the principles underpinning the AWS Enterprise Cloud Design Patterns, there are four of them:

  1. The goal is to leverage AWS cloud as an extension of the company's IT and not as the magic box that'll miraculously monetize your applications.

  2. Tackling cloud migration as IT infrastructure transition to AWS provides more value than narrowing it to migrating discrete applications.

  3. AWS Enterprise Cloud is made up of five building blocks associated with a design patterns: Extended VPC, Extended EC2, xSecurity, xFault Tolerance, and xStorage.

  4. Build on AWS Site-to-Site VPN Connection to address interactions with on-premise infrastructures.

What you must keep in mind is, the AWS Enterprise Cloud design patterns cut in half AWS architecture design and implementation time. Here is why:

  • It provides an actionable AWS cloud blueprint that works for 90% of digital transformations cases.

  • The five design patterns address the key issues to address including the hosting environment, network connectivity, computing power and reliability, efficient data storage, and security.

  • Each design pattern is laser focused on the AWS services and features it needs to provide the expected functions and benefits.

 

Let's explore the five AWS enterprise cloud architecture design patterns!

 

The Extended VPC

 

The extended VPC design pattern primary purpose is to deliver a component that acts as the hosting environment for the company's virtual infrastructure resources. In addition, it seeks to ensure fast and secure network connectivity. 

The extended VPC builds on AWS standard VPC which aggregates Internet Gateway (IGW), Route 53, Network Access Control List (NACL), Route Tables (RT) as well as Public and Private Subnets

The Extended VPC is implemented as part of an Elastic Beanstalk, CodeDeploy or CodePipeline environment created and configured through a CloudFormation template.

 

The Extended EC2

 

The primary purpose of the Extended EC2 design pattern is to deliver a component that acts as a Virtual Server. In addition, it seeks to ensure efficient computing capacity.

The Extended EC2 aggregates services and features including EC2 Instance, Key Pairs, Security Groups, Placement Groups, Containers and builds on xFault Tolerance, xStorage, and xSecurity design patterns to guarantee reliability, secure data storage, and security.

It's implemented as part of an Elastic Beanstalk, CodeDeploy or CodePipeline environment created and configured through a CloudFormation template.

 

The Extended Fault Tolerance

 

The main goal of the xFault Tolerance design pattern is to deliver components that provide, as the name suggest, fault tolerance mechanisms including load balancing, backup, and restore mechanisms to Extended EC2 and xStorage building blocks.

The xFault Tolerance aggregates services and features including Elastic Load Balancer (ELB), Auto Scaling Group (ASG), and Route 53 Health Check to ensure high availability and reliability.

The xFault Tolerance is implemented as part of an Elastic Beanstalk, CodeDeploy or CodePipeline environment created and configured through a CloudFormation template. 

 

The Extended Storage

 

The primary purpose of the Extended Storage design pattern is to deliver components that act as Data Storage Capacity.

The Extended Storage design pattern aggregates services and features including EBS volume, S3, Redshift, RDS and NoSQL databases to provide safe storage capacity.

It's implemented as part of an Elastic Beanstalk, CodeDeploy or CodePipeline environment created and configured through a CloudFormation template.

 

The Extended Security

 

The primary purpose of the Extended Security design pattern is to deliver components that provide Security Capacity.

The Extended Security design pattern aggregates services and features like Identity Access Management (IAM) and  Security Group (SG) to ensure security at the extended EC2 level and VPC endpoint, NACL, and RT to guarantee security across the VPC.

It's implemented as part of an Elastic Beanstalk, CodeDeploy or CodePipeline environment created and configured through a CloudFormation template.

 

The Key Takeaways

 

The AWS Enterprise Cloud design patterns discussed in this article are, of course, a light version of what they are in reality. Their purpose, content, and the AWS services and features they use aren't set in stone; they evolve as AWS grows.

They are a powerful way of putting cloud architecture building blocks into context and their reusable nature increases by 80% the solution architect productivity.

 

Share on Facebook
Share on Twitter
Please reload

Featured Posts

Why 78% of DevOps Implementations Fail? Why Only 22% Succeed?

July 19, 2019

1/4
Please reload

Recent Posts
Please reload