Amazon AWS Quick Start CourseQuick Start for Enterprise Architects – Sample Content1
Sample ContentIntroduction to Cloud ConceptsInfrastructure as a Service (IAAS) How it is built
 How it Scales
 How it differs from the traditional datacentreAmazon Web Services (AWS) Main ComponentsA 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
Sample ContentGetting Hands on with AWSAccount BasicsMachine Images , Security Groups, Key PairsManagement Console, Query API, Command Line tools & PluginsPractical Exercise 1 Building a gold machine images & deploying to EC2Practical Exercise 2 Deploying a sample application and with monitoring and auto scaling3
Sample ContentArchitecting for the Cloud – Best PracticesHorizontal vs Vertical ScalingLoose couplingBuild for ElasticityDesign for FailureSecurity not just at the edgeSession strategies and FailoverSecurity Best PracticesThe AWS shared responsibility modelData security and encryptionAccess & Network Security4
Sample ContentVirtual Private Network (VPN)A tour of the new VPN featuresHybrid Cloud StrategiesDeployment StrategiesCloud Formation & Configuration Automation Summary and Discussions5
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 includeCPU & RAMData ( disk latency & throughput)Network (latency & throughput ) 6
Infrastructure as a Service Architecture (extract)7
Infrastructure as a Service Architecture (extract)Delivered through a variety of physical and virtual servicesWorkload most often delivered by virtual servers but not alwaysVirtualisation based mainly on  Xen Hypervisor and VMWare HypervisorAWS mainly is based on XEN with support for other VMTerremark Based on VMWare8
Infrastructure as a Service Architecture (extract)Workloads are designed to meet different server workload types such asWeb servers Application serversTransactional DatabasesDatabases may be IO boundApplication servers  may be CPU bound9
Infrastructure as a Service Architecture (extract)Many different ways to architect an IAAS Cloud but fall into two main categories:Cloud CentersService Infrastructures10
Infrastructure as a Service Architecture (extract)Cloud Centersare data centersin the cloudBased on industry standard approach familiar to existing infrastructure peopleIncluded idioms such asVLANsNetwork blocksHardware load balancers and firewalls File storage ( SAN & NAS ) 11
Infrastructure as a Service Architecture (extract)AWS is a Service InfrastructureA set of non standard web services such as S3 network storage uses S3 protocol and storage mechanismsMany other non standard services built for massive scaling for exampleSQSSimple DBSoftware Firewall and Load BalancingServices can be used individually or together to create applications12
Infrastructure as a Service Architecture (extract)AWS does not provide one network per customerEach server on its own small networkTraffic between servers is routedThis means it is highly scalableRestriction on layer 2 network ( broadcasts, multi-cast )13
Main AWS Components (extract)Messaging - Simple Queue Service (SQS)Amazon Web scale messaging serviceAny computer on the internet can add or read messages ( by permission)5 Simple Basic API callsCreateQueueSendMessageReceiveMessageChangeMessageVisibilityDeleteMessage14

Amazon AWS Quick start course

  • 1.
    Amazon AWS QuickStart CourseQuick Start for Enterprise Architects – Sample Content1
  • 2.
    Sample ContentIntroduction toCloud ConceptsInfrastructure as a Service (IAAS) How it is built
  • 3.
    How itScales
  • 4.
    How itdiffers from the traditional datacentreAmazon Web Services (AWS) Main ComponentsA 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 ContentGetting Handson with AWSAccount BasicsMachine Images , Security Groups, Key PairsManagement Console, Query API, Command Line tools & PluginsPractical Exercise 1 Building a gold machine images & deploying to EC2Practical Exercise 2 Deploying a sample application and with monitoring and auto scaling3
  • 6.
    Sample ContentArchitecting forthe Cloud – Best PracticesHorizontal vs Vertical ScalingLoose couplingBuild for ElasticityDesign for FailureSecurity not just at the edgeSession strategies and FailoverSecurity Best PracticesThe AWS shared responsibility modelData security and encryptionAccess & Network Security4
  • 7.
    Sample ContentVirtual PrivateNetwork (VPN)A tour of the new VPN featuresHybrid Cloud StrategiesDeployment StrategiesCloud Formation & Configuration Automation Summary and Discussions5
  • 8.
    Infrastructure as aService Architecture (extract)Cloud building block consist of units called variously application containers , workloads or resource pools with an amount of resources These includeCPU & RAMData ( disk latency & throughput)Network (latency & throughput ) 6
  • 9.
    Infrastructure as aService Architecture (extract)7
  • 10.
    Infrastructure as aService Architecture (extract)Delivered through a variety of physical and virtual servicesWorkload most often delivered by virtual servers but not alwaysVirtualisation based mainly on Xen Hypervisor and VMWare HypervisorAWS mainly is based on XEN with support for other VMTerremark Based on VMWare8
  • 11.
    Infrastructure as aService Architecture (extract)Workloads are designed to meet different server workload types such asWeb servers Application serversTransactional DatabasesDatabases may be IO boundApplication servers may be CPU bound9
  • 12.
    Infrastructure as aService Architecture (extract)Many different ways to architect an IAAS Cloud but fall into two main categories:Cloud CentersService Infrastructures10
  • 13.
    Infrastructure as aService Architecture (extract)Cloud Centersare data centersin the cloudBased on industry standard approach familiar to existing infrastructure peopleIncluded idioms such asVLANsNetwork blocksHardware load balancers and firewalls File storage ( SAN & NAS ) 11
  • 14.
    Infrastructure as aService Architecture (extract)AWS is a Service InfrastructureA set of non standard web services such as S3 network storage uses S3 protocol and storage mechanismsMany other non standard services built for massive scaling for exampleSQSSimple DBSoftware Firewall and Load BalancingServices can be used individually or together to create applications12
  • 15.
    Infrastructure as aService Architecture (extract)AWS does not provide one network per customerEach server on its own small networkTraffic between servers is routedThis means it is highly scalableRestriction on layer 2 network ( broadcasts, multi-cast )13
  • 16.
    Main AWS Components(extract)Messaging - Simple Queue Service (SQS)Amazon Web scale messaging serviceAny computer on the internet can add or read messages ( by permission)5 Simple Basic API callsCreateQueueSendMessageReceiveMessageChangeMessageVisibilityDeleteMessage14