PowerPoint Presentation
Project -Part A – GoGreen Insurance Company
GoGreen Insurance Company
‹#›
Welcome to Project 2: Designing a Cloud Solution.
This project is suitable as an individual or group project. For those educators that choose to complete this as a team project, team evaluation materials have been included in the project guide.
1
Project – Part A Overview
1
Analyze needs and current architecture.
Design an AWS solution meeting the requirements provided.
2
Determine solution details.
Create an architecture diagram illustrating the solution.
‹#›
In this project, students will analyze the needs of a fictitious company (GoGreen) and design an AWS solution meeting the requirements identified. To complete this evaluation, students document with their proposal for choices of regions, VPCs, subnets, AZs, and other architecting details.
Students will create an architecture diagram and present their proposed solution to obtain feedback.
Upon completion of the solution design, students will implement critical portions of the design in a lab environment based on lab documentation provided.
Project Objectives
Upon completion of this project, you will be able to:
Experience the communication challenges faced when attempting to apply technology as the solution to business problems.
Translate customer requirements into a proposed technical solution.
Create an architecture diagram of the proposed solution.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
In this project, you will have the opportunity to experience a simulated customer experience depicting a customer’s move from a traditional environment to a cloud solution.
Next, we will take the output of the customer meeting, the customer requirements, and translate them into a proposed technical solution. We will document that technical solution with an architecture diagram. An architectural diagram is a rich and rigorous diagram that illustrates the details of the solution you are recommending.
Upon completion of this project, you will be able to:
Understand and experience the communication challenges faced when attempting to apply technology as the solution to business problems.
Translate customer requirements into a proposed technical solution.
Create an architecture diagram of the proposed solution.
Present the proposed solution to the customer (fellow students assuming the role of customer).
Implement the solution approved by the customer.
3
Project Suggestions
Some thoughts on this project:
This project is to be done individually
The high level and detailed customer requirements should be reviewed.
A solution should be designed to address each of the requirements identified.
Worksheets have been included to guide the documentation process.
Architecture diagramming suggestions have been included.
It may be helpful to review the Academy Cloud Foundations service introduction slides as you work through the solution details.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Some thoughts on this project:
This project can be done individually or in in groups of 2-3 students.
The high level and detailed customer requirements should be reviewed.
A solution should be designed to address each of the requirements identified.
Worksheets have been included to guide the documentation process.
Architecture diagramming suggestions have been included.
Upon completion of solution design, a presentation of the results should be prepared and given to the class.
The class can be involved to evaluate the solution in terms of requirement fulfillment and solution accuracy.
It may be helpful to review the Academy Cloud Foundations service introduction slides as you work through the solution details.
Customer Introduction and Overview
‹#›
To enable you to prepare for the meeting the customer has provided some facts about their current situation and environments. Review this information to understand the customer environment.
5
GoGreen Insurance Company Background
Company: GoGreen Insurance Company
Locations: Europe, South America,
Southern California (headquarters)
Application: A CRM web application allows sales personnel to input and edit customer data. The application stores customer data and documents and converts the documents into multiple formats, for example, images for web and mobile formats.
Technical Details: 3-tier web app stores customer data and documents. Converts the documents into multiple formats (e.g. images for web/mobile)
Goal: GoGreen’s goal is to go “paperless” for all user data, documents, and pictures.
‹#›
Here is some background on the company:
GoGreen is a regional insurance company based in California.
Their headquarters is in southern California, with offices in Europe and South America.
Their application stores customer data and documents and converts the documents into multiple formats, for example, images for web and mobile formats.
The application allows sales personnel to input and edit customer data.
GoGreen has a 3-tier CRM web application that supports sales users in California, Europe, and South America.
GoGreen’s goal is to go “paperless” for all user data, documents, and pictures.
Company Background: GoGreen Insurance Company
GoGreen Insurance Company has hired you to architect an infrastructure in AWS to meet their application needs.
In preparation for your meeting with them, they provided information about their current environment.
‹#›
GoGreen Insurance Company has hired you to architect an infrastructure in AWS to meet their application needs. In preparation for your meeting with them, they provided some information about their current environment.
Application Tier:
Five virtual servers (Four vCPUs / 16-GB memory)
Red Hat Enterprise Linux8
Java SRE 7/Java application files
GoGreen Insurance: Current Environment
Web Tier:
Six virtual machines (Two vCPUs / 4-GB memory)
Red Hat Enterprise Linux 8
Apache Tomcat web service
PHP server and PHP files
Database Tier:
Two virtual machines (Eight vCPUs / 32-GB memory / 5.5-TB storage)
Red Hat Enterprise Linux 8
MySQL 5.7.22 database cluster
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
For your preparations, the customer provided this information about their current architecture.
The current architecture has three tiers: a web tier, a database tier, and an application tier. They are configured as follows:
Web Tier
Six virtual machines (Two vCPUs / 4-GB memory)
Red Hat Enterprise Linux 8
Apache Tomcat web service
PHP server and PHP files
Application Tier
Five virtual servers (Four vCPUs / 16-GB memory)
Red Hat Enterprise Linux 8
Java SRE 7/Java application files
Database Tier
Two virtual machines (Eight vCPUs/ 32-GB memory / 5.5-TB storage)
Red Hat Enterprise Linux 8
MySQL 5.7.22 database cluster
8
Issues with the Current GoGreen Solution
On-premises performance and reliability issues frequently occur. This negatively impacts the user experience.
The architecture is continuously over-provisioned to try to handle growth and performance issues.
The architecture has been upgraded three times in the last year to accommodate growth:
The procurement process takes 20 days.
Deployment takes a week.
Growing the architecture is expensive — the entire process costs in excess of $100,000.
‹#›
Problems with the existing application include:
On-premises performance and reliability issues occur.
The architecture is continuously overprovisioned to try to handle growth and performance issues.
The architecture has been upgraded three times in the last year to accommodate growth:
The procurement process takes 20 days.
Deployment takes a week.
Growing the architecture has become too expensive — the entire process costs in excess of $100,000.
Customer Requirements and Solution Design Worksheets
‹#›
You have returned to the office with your teammates to discuss the GoGreen’s requirements. Now, it is time to turn all of those requirements into a solution design.
For ease of use, the customer requirements have been integrated with the solution design worksheets that can be used to document your solution.
10
GoGreen Insurance Company Requirements
The environment requirements include:
Infrastructure managed by members of the new Cloud Team.
Encryption for data in transit and at rest.
Secured access and identity management.
Stateless web servers for user connections.
Baseline identified for the number and type of instances needed.
Recovery Point Objective (RPO) for the application is four hours.
Scalability that accommodates user base growth of 90% in the next three years.
Storage for documents and pictures that must be kept five years. Note: these files are rarely requested after three months but infrequent access is still required.
Use of managed services to enhance availability and lower costs.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Based on the discussions and current architecture diagrams, the Solutions Architects and GoGreen Insurance Company arrived at the following customer requirements:
Infrastructure managed by members of the new Cloud Team.
Encryption for data in transit and at rest.
Secured access and identity management.
Baseline identified for the number and type of instances needed.
Recovery Point Objective (RPO) for the application is four hours.
Scalability that accommodates user base growth of 90% in the next three years.
Storage for documents and pictures that must be kept five years. Note: these files are rarely requested after three months but infrequent access is still required.
Use of managed services to enhance availability and lower costs.
GoGreen Insurance Company Project Objectives
Determine the region, VPCs, subnets, and Availability Zone requirements.
Document encryption and security details.
Design a plan for storage and backups.
Using what you learned in class, determine how to resolve the issues concerning the Web, App, and Database Tiers.
Document your implementation plan with an architecture diagram.
Build the infrastructure in the lab based on your design. (Project Part B – Optional)
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Based on the customer requirements, the following project objectives have been identified:
Determine the region, VPCs, subnets, and Availability Zone requirements.
Document encryption and security details.
Design a plan for storage and backups.
Using what you learned in class, determine how to resolve the issues concerning the Web, App, and Database Tiers.
Document your implementation plan with an architecture diagram.
Build the infrastructure in the lab based on your design.
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
Solution – Identify AWS Services
Identify the POTENTIAL services needed and the purpose for each service that will be used to move Go Green’s current environment to AWS.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Make a list of potential services. Describe why it was selected and how it addresses a GoGreen requirement. For example, we know that we need to manage user access. AWS Identity and Access Management (IAM would enable us to do that.
13
Detailed Requirements – User Authentication
All other users should only have AWS Management Console access, using a combination of user name and password.
Password Policy:
A password with at least 8 characters, 1 uppercase and 1 lowercase letter, 1 number, and 1 special character
Forced password change every 90 days
No re-use of previous three passwords
The GoGreen application must read and write to S3 buckets.
Follow AWS best practices for assigning permissions.
Three user groups with AWS access:
System Administrator Group: 2 users
Database Administrator Group: 2 users
Monitoring Group: monitors 4 users
Infrastructure resources (EC2, S3, RDS for the app)
Administrators require programmatic access and AWS Management Console access.
When signing in to the console, each administrator is required to provide a user name, a password, and a random generated code provided by the Virtual MFA.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Now, let’s take a look at the detailed requirements that have been identified.
The detailed requirements for user authentication are as follows:
There should be three user groups with AWS access:
System Administrator Group: 2 users
Database Administrator Group: 2 users
Monitoring Group (monitors 4 users): infrastructure resources (EC2, S3, RDS for the app)
Administrators require programmatic access and AWS Management Console access.
When signing in to the console, each administrator is required to provide a user name, a password, and a random generated code provided by the Virtual MFA.
All other users should only have AWS Management Console access, using a combination of user name and password.
The password policy should be as follows:
Uppercase and 1 lowercase letter, 1 number, and 1 special character
Forced password change every 90 days
No re-use of previous three passwords
The GoGreen application must read and write to S3 buckets.
14
Solution – User Authentication
Use this chart to document users, groups, and roles that need to be created.
Group: SysAdmin
Group: DBAdmin
Group: Monitor
GoGreen Insurance Company Account
Role: EC2toS3IAMRole
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use this chart to document the users, groups, and roles that need to be created.
15
Solution – User Authentication
Use this chart to document the groups and their associated permissions.
Group/Role # Group/Role Name Permissions
Group SysAdmin
Group DBAdmin
Group Monitor
Role EC2toS3IAMRole
You need to evaluate the associated permissions with each group and capture the actions that are allowed.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use this chart to document the groups and their associated permissions.
16
Solution – User Authentication
Use this chart to identify solutions for each requirement.
Requirement Solution
Should be at least 8 characters and have 1 uppercase, 1 lowercase, 1 special character, and a number.
Change passwords every 90 days and ensure that the previous three passwords can’t be re-used.
All administrators require programmatic access.
Administrator sign-in to the AWS Management Console requires the use of Virtual MFA.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use this chart to document solutions for each of the password requirements.
17
GoGreen Web Tier Requirements
Web Tier requirements include:
Architecture must be flexible and handle any peak in traffic or performance.
Current Servers at at 75% of memory capacity all the time. Memory capacity should be between 50% and 60%.
Application administrators want to be notified by email if there are more than 100 “400 HTTP errors” per minute in the application.
Web Tier instances should be tagged as “Key=Name” and “Value=web-tier”.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Now, let’s take a look at the Web Tier requirements.
Based on the discussions and current architecture diagrams, the Solutions Architects and GoGreen Insurance Company arrived at the following Web Tier customer requirements:
Architecture must be flexible and handle any peak in traffic or performance.
Current Servers at at 75% of memory capacity all the time. Memory capacity should be between 50% and 60%.
Application administrators want to be notified by email if there are more than 100 “400 HTTP errors” per minute in the application.
Web Tier instances should be tagged as “Key=Name” and “Value=web-tier”.
Design a solution that addresses these Web Tier requirements.
Design: Web Tier
Based on the requirements, describe the web tier solution.
Requirement Solution
Architecture must be flexible and handle any peak in traffic or performance.
The overall acceptable incoming network bandwidth is between 300 Mbps and 750 Mbps.
Application administrators want to be notified by email if there are more than 100 “400 HTTP errors” per minute in the application.
Web Tier instances should be tagged as “Key=Name” and “Value=web-tier
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Based on the requirements, describe the web tier solution.
19
GoGreen Application Tier Requirements
Application Tier requirements include:
Architecture must be flexible and handle any peak in performance.
Servers are currently at 90% of memory and CPU capacity all the time. Server capacity should be between 50% and 60%.
Memory and CPU utilization should not go above 80% and 75% respectively, or below 30% for each.
Internet access for patching and updates must be available without exposing the servers.
Application Tier instances should be tagged as “Key=Name” and “Value=app-tier”.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Now, let’s take a look at the Application Tier requirements.
Based on the discussions and current architecture diagrams, the Solutions Architects and GoGreen Insurance Company arrived at the following Application Tier customer requirements:
Architecture must be flexible and handle any peak in performance.
Servers are currently at 90% of memory and CPU capacity all the time. Server capacity should be between 50% and 60%.
Memory and CPU utilization should not go above 80% and 75% respectively, or below 30% for each.
Internet access for patching and updates must be available without exposing the servers.
Application Tier instances should be tagged as “Key=Name” and “Value=app-tier”.
Design a solution that addresses these Application Tier requirements.
Design: Application Tier
Based on the requirements, describe the application tier solution.
Requirement Solution
Architecture must be flexible and handle any peak in traffic or performance.
Server capacity should be between 50% and 60%.
Overall memory and CPU utilization should not go above 80% and 75% respectively or below 30% for either.
Internet access is required for patching and updates without exposing the servers.
Application Tier instances should be tagged as “Key=Name” and “Value=app-tier”.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Based on the requirements, describe the application tier solution.
21
GoGreen Insurance Company Requirements
The Database Tier requirements include:
The database needs consistent storage performance at 21,000 IOPS.
Ability to patch and update must be available.
High availability is a requirement.
Database schema can not be changed at at this time.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Now, let’s take a look at the Database Tier requirements.
Based on the discussions and current architecture diagrams, the Solutions Architects and GoGreen Insurance Company arrived at the following Database Tier customer requirements:
The database needs consistent storage performance at 21,000 IOPS.
Ability to patch and update must be available.
High availability is a requirement.
Database schema can not be changed at at this time.
Design a solution that addresses these Database Tier requirements.
Design: Database Tier
Based on the requirements, describe the database tier solution.
Requirement Solution
Database needs consistent storage performance at 21,000 IOPS.
High availability is a requirement.
No change to the database schema can be made at this time.
Note: Though the GoGreen business requires you to use a volume that supports 21,000 IOPS, in the lab environment you are restricted to only use General Purpose EBS volume type.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Based on the requirements, describe the database tier solution. (In the lab, use a T type instance for demo).
23
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
Design – Additional AWS Services
List any ADDITIONAL AWS services you would use for your solution and a justification for their use.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
List any ADDITIONAL AWS services you would use for your solution and a justification for their use.
24
Start with the structure
Determine where your diagram will be used. Websites and blogs will generally use a light background, whereas presentations tend to use a dark background. Locate the group type created for the appropriate background, then paste them onto your desired slide.
Add product and resource icons
Navigate to the category of your desired product icon or resource, then copy and paste it into your diagram.
Add other steps
Does your diagram include external users or devices? Use the illustrations to add depth or context to your diagram.
Connect the steps
Use the preset arrows to connect your steps and describe a workflow.
Creating an Architecture Diagram
‹#›
Based on your solution, construct a diagram of the proposed architecture.
Architecture diagrams are a great way to communicate your design, deployment and topology. AWS Simple Icons for Architecture Diagrams can be downloaded from: http://aws.amazon.com/architecture/icons/. This official collection of AWS product icons, resources, and other tools to help you build AWS architecture diagrams.
Customers and partners are permitted by AWS to use the resources to create architecture diagrams. The icons are designed to be simple so that you can easily incorporate them in your diagrams and put them in your whitepapers, presentations, datasheets, posters or any technical material you like.
When creating a diagram:
Start with the structure
Determine where your diagram will be used. Websites and blogs will generally use a light background, whereas presentations tend to use a dark background. Locate the group type created for the appropriate background, then paste them onto your desired slide.
Add product and resource icons
Navigate to the category of your desired product icon or resource, then copy and paste it into your diagram.
Add other steps
Does your diagram include external users or devices? Use the illustrations to add depth or context to your diagram.
Connect the steps
Use the preset arrows to connect your steps and describe a workflow.
AWS Simple Icons for Architecture Diagrams can be downloaded from: http://aws.amazon.com/architecture/icons/. The Microsoft Powerpoint version found there contains some extra diagramming insight.
Design – Network
Document the VPC solution.
VPC Region Purpose Subnets AZs CIDR Range
1
2
Subnet Name VPC Subnet Type (Public/private) AZ Subnet Address
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use this chart to document the details of the VPC solution.
26
Proposed Architecture Diagram
Construct a diagram of the proposed architecture.
(NB: Submit this as a separate file)
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Based on your solution, construct a diagram of the remaining architecture elements.
Design – Security
Document the security solution.
Security Group (SG) SG Name Rule Source
ELB load balancer
Web Tier
App Tier
Database Tier
Other Security Options Justification
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use this chart to document the security solution.
28
Design – Encryption
Document the encryption options.
Requirement Solution
Encryption option for
data at rest
Encryption option for
data in transit
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use this chart to document the encryption solution.
29
Design – Instance Details
Tier AMI Tag Type Size Justification # of instances
Web Key: Name
Value: app-tier
App Key: Name
Value: web-tier
DB N/A
Describe the needed type, size, and justification for the instances in each tier.
Note: You are required to capture the instance details per GoGreen’s current requirements. In the lab environment you are only allowed to use T instance types and General Purpose EBS volume type.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Describe the type, size, and justification for the instance you will use for each tier.
30
Design: Recovery Point Objective
Q. How would you achieve a Recovery Point Objective (RPO) of four hours?
A.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Describe how you would achieve a Recovery Point Objective (RPO) of four hours.
31
Design: Document Storage
Storage/Archive Option Detail
Based on the requirements, describe the document storage solution.
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Describe your design for the document storage based on the requirements.
32
GoGreen Insurance Company Cost Considerations (Optional)
The proposed solution should use the most cost-conscious financial options. What are the cost considerations?
‹#›
© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
The proposed solution should use the most cost-conscious financial options. What are the cost considerations?
© 2018 Amazon Web Services, Inc. or its affiliates. All rights reserved. This work may not be reproduced or redistributed, in whole or in part, without prior written permission from Amazon Web Services, Inc. Commercial copying, lending, or selling is prohibited. Corrections or feedback on the course, please email us at: aws-course-feedback@amazon.com. For all other questions, contact us at: https://aws.amazon.com/contact-us/aws-training/. All trademarks are the property of their owners.
Thanks for participating!
‹#›
Thanks for participating!