[Mar AWS 201] Technical Workshop
Upcoming SlideShare
Loading in...5
×
 

[Mar AWS 201] Technical Workshop

on

  • 588 views

 

Statistics

Views

Total Views
588
Views on SlideShare
588
Embed Views
0

Actions

Likes
0
Downloads
299
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

[Mar AWS 201] Technical Workshop [Mar AWS 201] Technical Workshop Presentation Transcript

  • amazon web servicesAWS 201T WorkshopDAY-1 (March 20): James Saull / Solutions Architect / jsaull@amazon.comDAY-2 (March 21): Session-1: 이수형 / Solutions Architect / niclee@amazon.com Session-2: 김일호 / Solutions Architect / ilho@amazon.com Session-3: 정윤진 / Solutions Architect / younjin@amazon.com
  • Agenda•  House Keeping & Setup •  Lab: Scalability and•  Introduction to Amazon Web Availability Services –  Snapshots•  Lab: Building a Web –  Load Balancing Property on AWS –  Auto Scaling –  Storage: S3, EBS –  Security –  Compute •  Log Processing Scenario –  Content Delivery –  Logging to AWS –  Relational Database –  Elastic Map Reduce –  Dynamo DB
  • Setup•  aws.amazon.com•  Be sure you have permissions and are active•  Latest browser•  Windows download Putty: www.putty.org
  • Watch out for unexpected CostsWhen the Technical Workshop comes to an end, toavoid unwanted costs:•  Delete your S3 objects•  Destroy your CloudFront distributions•  Stop or Shut Down your EC2 and RDS instancesThe customer is responsible for the resources he’susing. AWS declines any responsibility if the customerforgets to shut down resources.
  • Agenda•  House Keeping & Setup •  Lab: Scalability and•  Introduction to Amazon Web Availability Services –  Snapshots•  Lab: Building a Web –  Load Balancing Property on AWS –  Auto Scaling –  Storage: S3, EBS –  Security –  Compute •  Log Processing Scenario –  Content Delivery –  Logging to AWS –  Relational Database –  Elastic Map Reduce –  Dynamo DB
  • Region   GovCloud   R egion  [ Global AWS Infrastructure ]6
  • Availability   Z one  [ Global AWS Infrastructure ]7
  • 8  
  • SeaEle   South  Bend   New  York  (3)   London  (2)   Amsterdam  (2)   Newark   Dublin   Stockholm   Palo  Alto   Tokyo  (2)   Hayward  San  Jose   Paris   Frankfurt  (2)   Ashburn  (2)   (2)   Madrid   Milan   Los  Angeles  (2)   Jacksonville   Osaka   Hong  Kong   Dallas  (2)     (2)   St.Louis   Miami   Singapore   (2)   Sao  Paulo   Edge   L oca8ons   Sydney   [ Global AWS Infrastructure ] 9
  • amazon web services[ The Amazon Web Services universe ] 10
  • Command  Line   API   Web  Console   SDK  [ The Amazon Web Services universe ] 11
  • Cross Service Features CloudWatch  Simple  No8fica8on  Service   IAM   Simple  WorkFlow   CloudForma8on   Management + Elas8c  BeanStalk   Interface[ The Amazon Web Services universe ] 12 (some   s ervices   a re   o miEed   h ere)  
  • Cross Service Features Platform Building blocks EMR  RedshiX   SQS   CloudFront   Management + DynamoDB   Interface RDS   SES   CloudSearch  [ The Amazon Web Services universe ] 13 (some   s ervices   a re   o miEed   h ere)  
  • Cross Service Features Platform Building blocks Infrastructure Building Management + Blocks Interface EC2   Virtual  Private  Cloud   S3   Glacier   EBS  [ The Amazon Web Services universe ] 14 (some   s ervices   a re   o miEed   h ere)  
  • Elas8c  Beanstalk   Cross Simple  WorkFlow   Service CloudForma8on   CloudWatch         Features IAM   Command  Line   Web  Console   Platform APIs   SDK   Building RDS    CloudSearch   SES    CloudFront    SQS   blocks EMR    DynamoDB       Infrastructure Building Management + VPC      EC2   Blocks EBS      S3   Interface[ The Amazon Web Services universe ] (some   s ervices   a re   o miEed   h ere)  
  • Agenda•  House Keeping & Setup •  Lab: Scalability and•  Introduction to Amazon Web Availability Services –  Snapshots•  Lab: Building a Web –  Load Balancing Property on AWS –  Auto Scaling –  Storage: S3, EBS –  Security –  Compute •  Log Processing Scenario –  Content Delivery –  Logging to AWS –  Relational Database –  Elastic Map Reduce –  Dynamo DB
  • LabsDuring this workshop, we will build from scratch a highly available, redundant, scalable web property on AWS.
  • Our Building Blocks StorageAmazon  Simple  Storage  Service  (S3)   Amazon  Elas8c  Block  Storage  (Amazon  EBS)   Amazon  S3   Bucket   Amazon Elastic Volume Snapshot Block Storage (EBS)
  • Our Building Blocks Compute Amazon  Elas8c  Compute  Cloud  (EC2)  Amazon  EC2   Instance   Instances   AMI   DB  on   Instance  with   Elas8c  IP   Instance   CloudWatch  
  • Our Building Blocks Content Delivery & Database Amazon  Cloudfront   Amazon  Database  Services  RDS/DDB   Amazon   Download   Streaming   Edge  Loca8on   Amazon  RDS   MySQL  DB  Instance   DynamoDB  Cloudfront   Distribu8on   Distribu8on  
  • Amazon S3 Simple Storage Service•  Object-based storage •  Scalable (no Filesystem) •  Redundancy is managed•  Easily store/retrieve data transparently•  Durability of 99.999999999% •  File (Object): up to 5 TB each or 99.99% •  HTTP, HTTPS, BitTorrent•  Integrated with other AWS protocols Services 21
  • Amazon S3 Use cases•  Backup•  Archive (Glacier)•  Disaster Recovery (DR)•  Content Storage•  Website 22
  • Lab Exercise•  Create an S3 Bucket•  Upload and Download a File•  Check out properties and permissions
  • Questions ?
  • Amazon CloudFront Content Delivery Network•  Delivery of content •  Origin server: S3, EC2, worldwide non-AWS•  Static: HTTP / HTTPS •  Public/Private•  Streaming: RTMP Distributions•  Dynamic Content 25
  • Regions, Availability Zones, Edge Locations Amsterdam   SeaEle   South  Bend   New  York  (2)   London   Newark   Stockholm   Palo  Alto   Dublin   Tokyo  San  Jose   Frankfurt   Paris   Los  Angeles  (2)   Ashburn   Jacksonville   Hong  Kong   Dallas   St.Louis   Singapore   Sydney   Miami   Sao  Paulo   38  Edge  Loca8ons  in  total  (as  of  Dec  2012)  
  • Let’s simplify a bit: we consider only a few of them Stockholm  San  Jose   Hong  Kong   Sao  Paulo   Your  web  servers   in  Singapore  
  • Content Delivery Network: How it works Stockholm  San  Jose   Hong  Kong   Sao  Paulo   Dynamic  pages  (PHP,  Java)  (from  web  servers)   Your  web  servers   Sta8c  content  or  streaming  (with  CloudFront)   in  Singapore  
  • Amazon CloudFront Use cases•  Accelerated web content delivery•  Off-load traffic from web servers•  Big spikes in traffic•  Event streaming•  Marketing campaigns 29
  • Lab Exercise•  Create a New Distribution•  Test the Content
  • Questions ?
  • Amazon EC2 Elastic Compute Cloud•  Linux / Windows virtual Image machines •  VPC: Virtual Private Cloud•  Elastic (scale in minutes) •  Security (Groups, Keys...)•  Many Instance types •  VM Import (micro, small, large...) •  Auto Scaling, Elastic Load•  AMI: Amazon Machine Balancing 32
  • Availability   Z one  I see 20 Availability Zones in total (as of Feb 2013) 33
  • EC2 Use cases•  Media •  Internal Applications•  Hosting •  Gaming•  High Performance •  ... Everything that Computing needs computing!•  Dev & Test 34
  • Lab Exercise•  Create a new Security Group•  Launch an Amazon EC2 instance (Linux)•  Log in with SSH as ec2-user@•  Install a web server•  Create a simple web page•  Test it on a browser: it works!•  Create and attach an Elastic IP
  • Questions ?
  • EBS Elastic Block Storage•  Block Level Storage for use •  Redundant with EC2 •  Persistent•  Volume: 1 GB to 1 TB •  Point-in-time snapshots to•  Raw unformatted block Amazon S3 device •  Integration with CloudWatch•  Local to an Availability Zone 37
  • Demo EBS•  Create a new EBS volume•  Attach it to an EC2 Instance•  Partition it and create a File System•  Mount it; create a file in it•  Create an EBS Snapshot•  Create a new volume from the Snapshot
  • Questions ?
  • RDS Relational Database Service•  Relational Database “as a •  Optional: automatic Standby Service” Replica•  Simple to Deploy •  Optional: multiple Read-Only•  Managed by the AWS team copies•  MySQL, SQLServer or •  Easy DB Snapshots and Oracle (as of 2012) automated backup•  Scalable 40
  • Demo RDS•  Create a DB Instance on RDS (MySQL)•  Enable Multi-AZ Deployment•  Enable one Read Replica•  Optional: connect to the DB Instance
  • Questions ?
  • Agenda•  House Keeping & Setup •  Lab: Scalability and•  Introduction to Amazon Web Availability Services –  Snapshots•  Lab: Building a Web –  Load Balancing Property on AWS –  Auto Scaling –  Storage: S3, EBS –  Security –  Compute •  Log Processing Scenario –  Content Delivery –  Logging to AWS –  Relational Database –  Elastic Map Reduce –  Dynamo DB
  • Let’s take our WebApplication to the next level
  • EBS Elastic Load Balancer•  Automatically distribute incoming traffic to multiple Amazon EC2 instances (in the same Region).•  Automatic Health check•  IPv6 support•  Can be integrated with AutoScaling
  • Questions ?
  • Snapshots & AMIs•  Copies of EBS Volumes•  Essential to Reusability•  Copy between Regions•  Durability in S3
  • Lab Exercise•  Duplicate your entire architecture by making an AMI•  Increase your availability by spreading your application across availability zones•  Bring up an ELB in front of your website•  Optional – Create a CNAME to the ELB
  • Questions ?
  • CloudWatch•  Integrated across AWS platform•  Nothing to install•  Custom Metrics•  Set Alarms•  View graphs and statistics•  Feeds into Autoscaling
  • AutoScaling•  Auto Up and Auto Down•  Runs on CloudWatch metrics•  Notifications via SNS•  Spot or On-demand•  No additional Fees
  • AutoScaling•  Launch config: AMI to be used•  Autoscaling group: where/how to launch•  Autoscaling policy: what should AS do•  Autoscaling trigger: what will activate AS
  • Demo Autoscaling JMETER  
  • Questions ?
  • Security•  Security Groups•  Granular tiered secure architecture•  Roles for services•  Best Practices - Bastions
  • Before we get started on the controls…•  AWS Reports, Certifications & Accreditations •  SOC 1, Type 2 report •  SOC 2 report •  ISO 27001 •  PCI DSS Level 1 service provider •  FISMA Moderate •  MPAA•  Look at http://aws.amazon.com/security
  • A ProtectedInfrastructure: IAM VPC ACL ELB AZ SG TMG RDP WSUS
  • Lab Exercise•  Secure your website by creating a DMZ between the ELB and your application•  Create a bastion host
  • Questions ?
  • Agenda•  House Keeping & Setup •  Lab: Scalability and•  Introduction to Amazon Web Availability Services –  Snapshots•  Lab: Building a Web –  Load Balancing Property on AWS –  Auto Scaling –  Storage: S3, EBS –  Security –  Compute •  Log Processing Scenario –  Content Delivery –  Logging to AWS –  Relational Database –  Elastic Map Reduce –  Dynamo DB
  • Getting your Data into S3 Console Upload S3 3rd Party Commercial Applications FTP Tsunami UDP AWS Import / Export Storage Gateway Flume S3 API CloudFront Direct Connect AWS Data Pipeline
  • S3 and Big Data•  Why S3?•  Hadoop Overview•  Hadoop on the Cloud•  Hadoop File System
  • Introducing Apache Hadoop•  Apache Hadoop •  Software for distributed data analysis •  Map/Reduce framework •  Focus on data
  • •  But •  Complex •  Hard to setup •  Cap-ex intensive •  Difficult to manage
  • What  is  Amazon  Elas3c  MapReduce  (EMR)?   EMR  is  Hadoop  in  the  Cloud   Hadoop  is  an  open-­‐source  framework  for   parallel  processing  huge  amounts  of  data  on   a  cluster  of  machines  
  • How does it work? Choose:  Hadoop  distribu8on,  #   of  nodes,  types  of  nodes,  custom   configs,  Hive/Pig/etc.  Put  the  data   into  S3   S3 EMR  Cluster 011001101   EMR Launch  the  cluster  using   the  EMR  console,  CLI,  SDK,   or  APIs   Get  the  output   from  S3   You  can  also  store   everything  in  HDFS  
  • DynamoDB and Big Data•  What is Dynamo?•  Dynamo in Big Data – Volume & Velocity
  • Questions ?
  • Watch out for unexpected CostsWhen the Technical Workshop comes to an end, toavoid unwanted costs:•  Delete your S3 objects•  Destroy your CloudFront distributions•  Stop or Shut Down your EC2 and RDS instancesThe customer is responsible for the resources he’susing. AWS declines any responsibility if the customerforgets to shut down resources.
  • amazon web services Thank YouDAY-1 (March 20): James Saull / Solutions Architect / jsaull@amazon.comDAY-2 (March 21): Session-1: 이수형 / Solutions Architect / niclee@amazon.com Session-2: 김일호 / Solutions Architect / ilho@amazon.com Session-3: 정윤진 / Solutions Architect / younjin@amazon.com