"Web Age Speaks!

" Webinar Series

Overview of Amazon Web

Services
Introduction

 Mikhail Vladimirov
 Director, Curriculum Architecture
 [Link]@[Link]
 Web Age Solutions
 Provider of a broad spectrum of regular and customized
training classes in programming, system administration and
architecture to clients across the world since 1999

©[Link] 2
Overview of Talk

 History of Amazon Web Services (AWS)

 AWS Management Console
 Overview of the core services, including:
 S3
 EC2
 EBS

©[Link] 3
Overview of Amazon Web Services

The History of AWS

 What is the Amazon Cloud?

 The Amazon Cloud offers a variety of infrastructure

services called Amazon Web Services (AWS) that
clients can start using with administration costs
significantly lower compared with those required to
support their own infrastructure
 The Benefits of using AWS Cloud services:
 Just-in-time infrastructure provisioning
 Pay-as-you go (usage-based) costing model
 Shorter time to market
 Innovation platform
 Efficient development cycle
• Cloning of environments is supported (Dev → QA → Staging →
Production)

©[Link] 5
 The History of AWS
 In 2003, Chris Pinkham and Benjamin Black of Amazon
presented a short internal paper "describing a vision for Amazon
infrastructure that was completely standardized, completely
automated, and relied extensively on web services for things
like storage" [[Link]
 The first public AWS service was Simple Queue Service (SQS)
launched in November 2004
 S3 was launched in March 2006
 EC2 followed with a launch in August 2006
 As a cloud platform providing on-line services for clients, AWS
was launched in 2006
 In November 2010, all of [Link] retail web services were
moved to AWS

©[Link] 6
[Link] AWS Infrastructure circa 2008

 [Link] web servers were moved to AWS in 2009/2010)

 Source: The "[Link]'s Journey to the Cloud" presentation
by Jon Jenkins [jjenkin@[Link]]

©[Link] 7
Overview of Amazon Web Services

The AWS Management Console

The AWS Management Console

©[Link] 9
Overview of Amazon Web Services

The Overview of AWS

The AWS Service Stack

Source: Amazon Web Services

©[Link] 11
The AWS Distributed Architecture
 The AWS cloud platform is deployed across a number
of geographical regions (11 as of beginning 2015)
 Each region includes several "Availability Zones" (AZ),
which are isolated from each other data centers
 Some Amazon services can operate across AZ's (e.g. S3)
 Other services require you to set up and configure
replication across AZ's to achieve service resilience against
data center outages
 As of December 2014, Amazon Web Services
operated 1.4 Million servers across 28 availability
zones.[ [Link] ]

©[Link] 12
The Amazon Web Services Overview
 Elastic Compute Cloud (EC2)
 The compute service of AWS
 Identity and Access Management (IAM)
 Helps managing users and their permissions within your
AWS Account
 IAM is natively integrated into all the AWS Services
 Virtual Private Cloud (VPC)
 Lets you define a private virtual network inside the AWS
Cloud with your own IP address range, subnets, route
tables, and network gateways
 Enables you to build hybrid clouds by extending your
corporate network topology into a private cloud inside the
Amazon Cloud
 AWS VPC uses IPSec tunnel mode for point-to-point secure
channel between your data center and the AWS Cloud

©[Link] 13
The Amazon Web Services Overview
 CloudWatch
 Helps with monitoring Amazon EC2 instances with respect of
operational performance, including such metrics as CPU
utilization, I/O operations, network traffic (in/out), response
latencies, HTTP status codes, etc.
 Auto-scaling Group
 Allows automatic scaling of your capacity by configuring
resource utilization thresholds and usage conditions
 Metrics are collected by the CloudWatch service
 Elastic Load Balancing
 Distributes incoming traffic across a cluster of EC2 instances
 Amazon Elastic Block Storage (EBS)
 A network-attached persistent storage volume(s) that you
can attach to EC2 instances

©[Link] 14
The Amazon Web Services Overview
 Simple Storage Service (S3)
 Highly durable distributed data store
 S3 supports the RESTful end-point as a programmatic
interface for uploading and downloading objects
 CloudFront
 A content delivery service for static and/or streaming
content
 S3 objects (images, documents, etc.) can be replicated and
cached using CloudFront in a number of different
geographical locations (called edges)
 SimpleDB
 A simple NoSQL engine that operates on collections of items
stored as key-value pairs

©[Link] 15
The Amazon Web Services Overview
 Relational Database Service (RDS)
 Backed-up by full-featured instances of a database engine of
your choice (databases currently supported are: MySQL,
Postgres, Oracle, SQL Server, and Amazon Aurora)
 Database administration tasks such as backups, patch
management, etc., are taken care of by AWS support
 Simple Queue Service (SQS)
 A cloud-grade distributed queuing system
 Supports JMS 1.1 API with minimal changes
 Simple Notifications Service (SNS)
 SNS allows you build applications based on the pub-sub
protocol (topics-based)

©[Link] 16
The Amazon Web Services Overview
 Elastic MapReduce (EMR)
 A hosted Hadoop framework for running MapReduce jobs
 You have a choice of Hadoop-related applications that can
be installed alongside with your Hadoop cluster:
• Hive, Pig, Hue, HBase, Impala, etc.
 In addition to the Amazon's Hadoop distribution based on
the open-source (and free) Hadoop packages, you have an
option to use MapR which is a more efficient, third-party
distribution from [Link]
• See [Link] for
details
 EMR is tightly integrated with EC2 and S3 services

©[Link] 17
The Amazon Web Services Overview
 Route53
 A highly scalable DNS service which you can use to manage
your DNS records for all your domains to help resolve
domain names to AWS-hosted IP addresses of your
applications
 It also provides ways to buy new domains and transfer in
existing domains
 Route 53 can also act as the registrar for your existing
domains that you bought from other registrars
 This service can also be used to monitor the health and
performance of your web applications and redirect traffic
accordingly

©[Link] 18
Overview of Amazon Web Services

Simple Storage Service (S3)

 S3
 S3 handles arbitrary objects from 1 byte up to 5
TB
 Every object can have up to 2 kilobytes of
metadata
 Objects are stored in buckets (containers) that
may be used to build a folder-like hierarchical
storage structure
 S3 exposes its functionality through the
command-line and web services interfaces
(REST, SOAP, and BitTorrent)
 Note: SOAP support over HTTP is deprecated and new
S3 features will not be supported for SOAP

©[Link] 20
S3 Bucket Configuration

©[Link] 21
S3 Object Lifecycle Configuration
 You can configure object lifecycle events, such as archiving, or
deleting objects (e.g. log files) after a specified time period
 Rules controlling lifecycle events are configured at the bucket
level and apply to the whole bucket
 You can define the following actions on objects:
 Archive Only
• And keep the object in S3
 Permanently Delete Only
 Archive and then Permanently Delete
• Essentially, move the object from S3 to the archive
 Here is a visual representation of a rule for archiving a file in the
Glacier archival storage after 1 day of holding it in S3:

©[Link] 22
 Static Web Hosting in S3
 You can host all the static content of your website on
Amazon S3
 The static content includes HTML pages, JavaScript and CSS
files, images, etc.
 You can refresh static content by uploading the updated
versions of those static content assets
 You configure website hosting at the bucket level
 Once you enable your bucket for static website
hosting, all your content in the bucket is publicly
accessible via the Amazon S3 HTTP endpoint at the
following sub-domain:
<your-bucket-name>.<your-region>.[Link]

©[Link] 23
 Manual File Upload to S3

©[Link] 24
 Object Permissions
 Objects in S3 are controlled by permissions and can
be exposed to the public view

©[Link] 25
 S3 Pricing
 US Standard:

 South America (Sao Paulo):

©[Link] 26
Overview of Amazon Web Services

Elastic Compute Cloud (EC2)

 EC2
 Amazon EC2 provides web-scale compute capability
 EC2 instances (deployed as virtual machines) are
bootable from an Amazon Machine Image (AMI) of
the operating system of your choice, which may
optionally have pre-installed software and associated
configuration files
 Currently, EC2 offers a selection of 500+ AMI's of popular
Open Source and commercial software, available from the
Amazon's marketplace
 You can also create your own AMI
 You have a wide range of supported OS images to
chose from:
 Various Linux distros
 Windows

©[Link] 28
AWS Marketplace for OSes

©[Link] 29
AWS Marketplace for Tools & Apps

©[Link] 30
 EC2 Instance Choices

 You have a choice of

 On-demand instances (regular price)
• You pay for the running instances by the hour
 Reserved instances (a cheaper choice)
• You make a low (compared with the on-demand instance),
one-time upfront payment
 Spot instances (the cheapest choice)
• You can bid for unused EC2 capacity, and get it when the price
slides below the desired threshold

©[Link] 31
 EC2 Instance Types
 AWS Cloud offers a wide selection of EC2 instance
types to help you match different use cases with
optimum computer capacity
 Instance types include such parameters as:
 CPU, RAM, instance storage, and networking capacity (all
resources are virtual!)
 Amazon recommends to measure the actual
performance of your application by running it under
load to identify the suitable instance type and
validate your solution architecture

©[Link] 32
 EC2 Instance Types Matrix
 EC2 instance types are grouped by instance families
that have similar base run-time profiles suitable for
specific use cases
 Within each family, you have models with more vCPUs, RAM
and storage
 Main families:
 T2 (General Purpose Category)
 M3 (General Purpose Category)
 C3 (Compute Optimized Category)
 R3 (Memory Optimized Category)
 G2 (Graphics Optimized Category)
 I2 (Storage Optimized Category)
 HS1 (Storage Optimized Category)
 Note: The original T1, M1, C1, CC2, M2, CR1, CG1, and HI1
instance types have been deprecated
©[Link] 33
The T2 Type: Example of a Low-end Type
 The T2 type is used for low compute capacity instances
 This type is suitable for development, prototyping, build
servers, and small web applications
 T2 instances are positioned as instances with "Burstable
Performance", meaning that they offer a baseline level
of CPU performance with the ability to burst above the
baseline for a short period of time

©[Link] 34
The I2 Type: Example of a High-end Type
 The I2 type is storage optimized with fast SSD-backed
instance storage optimized for random I/O performance
 This type gives you an option of very cost-efficient IOPS
rates and enhanced networking with great packet per
second (PPS) rate and low latencies
 Use cases: NoSQL systems (MongoDB, Cassandra,
Hadoop, etc.)

©[Link] 35
 VM Import / Export to/from EC2

 You can import your existing virtual machines into

Amazon EC2 by using the EC2 API (CLI) tools
 You can import the following VM types:
 VMware ESX and VMware Workstation VMDK images
 Citrix Xen VHD images
 Microsoft Hyper-V VHD images
• When you import your Microsoft Windows VM images, AWS will
provide the appropriate Microsoft Windows Server license key
for your VM
 You can also export previously imported EC2
instances

©[Link] 36
 EC2 Quotas

 Per region, you can run up to

 20 On-Demand Instances
 Buy and run 20 Reserved Instances
 Make a request for and run 5 Spot Instances

 If you wish to provision more instances, you need to

complete the Amazon EC2 instance request form

©[Link] 37
 Spot Instances
 The spot instance pricing fluctuates over a period of time
and availability zone
 You can check the Pricing History in the EC2 dashboard to
see the trend to better prepare for pricing changes
 You can select a time horizon (from 1 day up to 3
months), instance OS, and EC2 instance type per
availability zone

©[Link] 38
 EC2 SLA
 In its SLA, AWS makes a Service Commitment to this effect:
 "AWS will use commercially reasonable efforts to make Amazon
EC2 and Amazon EBS each available with a Monthly Uptime
Percentage of at least 99.95%, in each case during any
monthly billing cycle (the “Service Commitment”). In the event
Amazon EC2 or Amazon EBS does not meet the Service
Commitment, you will be eligible to receive a Service Credit as
described below."
 "Service Credits are calculated as a percentage of the total
charges paid by you (excluding one-time payments such as
upfront payments made for Reserved Instances) for either
Amazon EC2 or Amazon EBS"

©[Link] 39
Overview of Amazon Web Services

Amazon Elastic Block Store (EBS)

 EBS
 The Elastic Block Store (EBS) is a network-linked
persistent storage volume that you can attach to EC2
instances
 An EBS volume is seen by your EC2 instance as a
local hard drive
 Note: You will pay for this storage even if your
instance to which the volume is attached is stopped
 Launched EC2 instances also receive free local
instance store of limited capacity which is ephemeral
and gets recycled (totally erased) when the server is
stopped
 You should use the local instance store only for
temporary data that don't require durable persistence

©[Link] 41
 EBS
 EBS offers raw, unformatted block-level storage
 After you have attached an EBS volume, you will need to
format it and create a file system on the device before
you can start using it
 You may experience some I/O delays (5 to 50 %) when
starting to use a newly added EBS volume
 You may also experience spikes in CPU usage during such
times
 An EBS volume must be created in the same Availability
Zone as the EC2 instance you are going to attach the
volume to
 Each EBS volume is automatically replicated within its
Availability Zone (AZ) offering high guarantees of data
durability and protection against loss of your data

©[Link] 42
 Types of EBS
 EBS comes in three volume types that differ in
performance characteristics and cost
 Provisioned IOPS Solid-State Drives (SSD):
 The fastest option with 4,000 IOPS with single-digit millisecond
latencies
 Consistent performance
 Max throughput: 128MBps
 General Purpose (SSD):
 Have the ability to burst to 3,000 IOPS per volume
 Max throughput: 128MBps
 Magnetic Disk (used to be called the EBS Standard
Volume):
 The lowest cost volume with the slowest I/O throughput (several
hundred IOPS)
 Max throughput: 40-90MBps

©[Link] 43
 EBS Volume Encryption
 EBS volumes can be encrypted
 Applying EBS encryption may be required, for
example, in order to meet some regulatory security
compliance requirements for your data-at-rest
 Encryption is done using AWS-managed keys or keys
you create and manage using the AWS Key
Management Service
 Keys are protected by AWS key management infrastructure
 Each newly created EBS volume is issued a unique
256-bit AES key
 EBS volumes created from encrypted snapshots
inherit the key
 Currently, only data volume encryption is supported
(boot volumes cannot be encrypted)
©[Link] 44
 Use Cases for EBS Volume Types
 Provisioned IOPS (SSD)
 I/O Intensive systems: relational and NoSQL Databases
 General Purpose (SSD)
 Boot volumes, development, testing, small to medium
relational and NoSQL databases
 Magnetic Disk
 Low demand data access

©[Link] 45
 EBS Volume Type Prices

 Volume prices below are shown for the US East (N

Virginia) AZ
 Provisioned IOPS (SSD): $.125/GB - Month
 General Purpose (SSD): $.10/GB - Month
 Magnetic Disk: $.05/GB - Month

©[Link] 46
 Creating an EBS Volume

 EBS volumes must be created in the AZ of your EC2

instance that you want to attach the EBS volume to

1
2

©[Link] 47
 EBS Volume RAID Configuration
 EBS volumes can be joined in any of the standard RAID
configurations the same way as you would if you use
physical hard drives
 The selected RAID configuration must be supported by
the operating system installed on your EC2 instance as
RAID configuration is done at the software level
 Amazon recommends
 RAID 0 mode (disk striping, without mirroring or
parity) when I/O performance is more important than
fault tolerance
 RAID 1 (disk mirroring, without parity or striping)
mode when fault tolerance is more important than I/O
performance
 RAID 5 and RAID 6 are not recommended for Amazon
EBS because these modes take away some of the IOPS
available to your volumes for parity writing operations
©[Link] 48
 EBS Volume Snapshots
 EBS provides the ability to save the replica of the
volume as a point-in-time snapshot
 Only changes (delta) are saved in subsequent EBS
snapshots
 You only pay for the incremental delta in snapshots
 To fully restore the volume, you need all the active
snapshots
 You can access the Public Snapshots repository from
the list in the Snapshots section of the AWS
Management Console
 Snapshots are stored in S3
 When you start using an EBS volume created from an EBS
Snapshot, first hit on a required data block may be delayed
(the lazy loading model is implemented)

©[Link] 49
Use Cases for EBS Volume Snapshots

 Snapshots are used as

 The mechanism to move volumes across Availability Zones
 A base for creating new volumes
 A way to increase the size of a volume
 A point-in-time backups of your volumes

©[Link] 50
Overview of Amazon Web Services

Our Offerings
Cloud computing and solutions offerings

 WA2391 Amazon Web Services for Solution Architects

(2 days)

 WA1929 Cloud Essentials for Architects using

OpenStack (2 days)

©[Link] 52
Summary

In this session, we:

 Reviewed the key milestones in the history of AWS
 Provided a quick overview of the AWS Management Console
 Talked about some of the core Web Services, including:
• S3
• EC2
• EBS

©[Link] 53