Morgan Hill offers comprehensive training for the corporate, enterprise architect on the Amazon Web Services (AWS) platform. This AWS training is delivered by experienced architects used to operating in a corporate infrastructure environment.

1. Amazon AWS Quick Start Course Quick Start for Enterprise Architects – Sample Content 1

3. How it Scales

4. How it differs from the traditional datacentreAmazon Web Services (AWS) Main Components A detailed look at Elastic Compute (EC2) AMIs , Elastic Block Storage (EBS), Auto Scaling CloudWatch Elastic Load Balancers, Simple Storage (S3), Simple Queue Service (SQS), Simple Notification Service (SNS), Databases, Relational Database Service (RDS), SimpleDB, Virtual Private Network. Main use cases 2

5. Sample Content Getting Hands on with AWS Account Basics Machine Images , Security Groups, Key Pairs Management Console, Query API, Command Line tools & Plugins Practical Exercise 1 Building a gold machine images & deploying to EC2 Practical Exercise 2 Deploying a sample application and with monitoring and auto scaling 3

6. Sample Content Architecting for the Cloud – Best Practices Horizontal vs Vertical Scaling Loose coupling Build for Elasticity Design for Failure Security not just at the edge Session strategies and Failover Security Best Practices The AWS shared responsibility model Data security and encryption Access & Network Security 4

7. Sample Content Virtual Private Network (VPN) A tour of the new VPN features Hybrid Cloud Strategies Deployment Strategies Cloud Formation & Configuration Automation Summary and Discussions 5

8. Infrastructure as a Service Architecture (extract) Cloud building block consist of units called variously application containers , workloads or resource pools with an amount of resources These include CPU & RAM Data ( disk latency & throughput) Network (latency & throughput ) 6

9. Infrastructure as a Service Architecture (extract) 7

10. Infrastructure as a Service Architecture (extract) Delivered through a variety of physical and virtual services Workload most often delivered by virtual servers but not always Virtualisation based mainly on Xen Hypervisor and VMWare Hypervisor AWS mainly is based on XEN with support for other VM Terremark Based on VMWare 8

11. Infrastructure as a Service Architecture (extract) Workloads are designed to meet different server workload types such as Web servers Application servers Transactional Databases Databases may be IO bound Application servers may be CPU bound 9

12. Infrastructure as a Service Architecture (extract) Many different ways to architect an IAAS Cloud but fall into two main categories: Cloud Centers Service Infrastructures 10

13. Infrastructure as a Service Architecture (extract) Cloud Centersare data centersin the cloud Based on industry standard approach familiar to existing infrastructure people Included idioms such as VLANs Network blocks Hardware load balancers and firewalls File storage ( SAN & NAS ) 11

14. Infrastructure as a Service Architecture (extract) AWS is a Service Infrastructure A set of non standard web services such as S3 network storage uses S3 protocol and storage mechanisms Many other non standard services built for massive scaling for example SQS Simple DB Software Firewall and Load Balancing Services can be used individually or together to create applications 12

15. Infrastructure as a Service Architecture (extract) AWS does not provide one network per customer Each server on its own small network Traffic between servers is routed This means it is highly scalable Restriction on layer 2 network ( broadcasts, multi-cast ) 13

16. Main AWS Components (extract) Messaging - Simple Queue Service (SQS) Amazon Web scale messaging service Any computer on the internet can add or read messages ( by permission) 5 Simple Basic API calls CreateQueue SendMessage ReceiveMessage ChangeMessageVisibility DeleteMessage 14

17. Hands on with Elastic Cloud Compute (extract) Manual Auto scaling Launch resources into group Scale by schedule Scale by time and date around a predictable schedule For example: daytime, rush hour, night time Scale by Policy For example: Add server to the group if average CPU goes above 90% for more than 20 minutes Or remove a server from the group if it drops below 40% Metric based on alarms such as network, CPU and disk usage 15

19. At our offices

20. At a specific venue

21. Via Webex16