Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

AWS SSA Webinar 7 - Getting Started on AWS

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige

Hier ansehen

1 von 59 Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Ähnlich wie AWS SSA Webinar 7 - Getting Started on AWS (20)

Anzeige

Weitere von Cobus Bernard (20)

Aktuellste (20)

Anzeige

AWS SSA Webinar 7 - Getting Started on AWS

  1. 1. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Getting started with AWS O n l i n e W e b i n a r – 2 0 2 0 / 0 4 / 2 1 Cobus Bernard Sr Developer Advocate Amazon Web Services @cobusbernard cobusbernard cobusbernard
  2. 2. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Agenda Global infrastructure Security Networking Compute Storage Q&A
  3. 3. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS global platform AWS global infrastructure • 22 Regions with 70 Availability Zones • 5 Regions coming soon: Indonesia, Italy, South Africa, Spain and Osaka 216 CloudFront PoPs • 205 edge locations • 11 Regional edge caches • 245 Countries & territories served AWS global network • Redundant 100 GbE network • 100% encrypted between facilities • Private network capacity between all AWS Regions except China SLA of 99.99% availability
  4. 4. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS Region and availability zones Region Availability zone a Availability zone b Availability zone c data center data center data center 2 or more AZs per region (new regions min 3) data center data center data center data center data center data center 1 or more data centers per AZ
  5. 5. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Availability in parallel Component Availability Downtime X 99% (2-nines) 3 days 15 hours Two X in parallel 99.99% (4-nines) 52 minutes Three X in parallel 99.9999% (6-nines) 31 seconds
  6. 6. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
  7. 7. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS Identity and Access Management Security before the cloud Security in the cloud Corporate data center AWS Cloud 
  8. 8. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. IAM roles for nonhuman access AWS account Use IAM roles for access to AWS resources: • From your application running on an AWS compute environment, e.g., EC2 instance, Lambda function, etc. • To grant permission to an AWS service to access your resources (not shown) EC2 instance Lambda function Amazon S3 buckets Amazon DynamoDB table
  9. 9. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. There are many security services in AWS AWS Identity and Access Management (IAM)
  10. 10. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
  11. 11. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
  12. 12. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Private IP address range for your VPC – IPv4 • ”CIDR” range? • Classless inter-domain routing • No more class A, B, C • RFC1918 • 192.168.0.0 /16 • 172.16.0.0 /12 • 10.0.0.0 /8 • How much? • /16 • /28
  13. 13. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Subnet Subnet Subnet Subnet VPC Availability Zone US-EAST-1A Availability Zone US-EAST-1B Amazon VPC (Virtual Private Cloud) 172.31. 172.31. 172.31. 172.31. Subnet Subnet Availability Zone US-EAST-1C 172.31. 172.31. 172.31.0.0/16: 172.31.0.1 to 172.31.255.254 = 65534 host IPs /24 = 254 hosts /20 = 4096 hosts
  14. 14. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Subnet Subnet Subnet VPC Availability Zone US-EAST-1A Availability Zone US-EAST-1B Amazon VPC (Virtual Private Cloud) 172.31. 172.31. 172.31. 172.31. Subnet Subnet Availability Zone US-EAST-1C 172.31. 172.31. Application server security group
  15. 15. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Subnet Subnet VPC Availability Zone US-EAST-1A Amazon VPC (Virtual Private Cloud) 172.31. 172.31. Subnet Subnet 172.31. 172.31. Web server security group Application server security group Availability Zone US-EAST-1C
  16. 16. What is Amazon CloudFront? CloudFront is the AWS content delivery network It securely delivers data, videos, applications, and APIs to customers globally with low latency and high transfer speeds CloudFront is integrated with AWS; physical locations are directly connected to the AWS Global Cloud Infrastructure and other AWS services It features a global network of >200 points of presence (PoPs)
  17. 17. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Latency benefits with PoP launches Argentina 55% Latency reduction 79 ms  35 ms Chile 73% Latency reduction 104 ms  28 ms PoP launches ensure connectivity with majority views and redundant AWS backbone Bahrain: 40% Latency reduction 38 ms  27 ms
  18. 18. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Learn networking with AWS Training and Certification Free digital courses cover topics related to networking and content delivery, including Introduction to Amazon CloudFront and AWS Transit Gateway Networking and Scaling Resources created by the experts at AWS to help you build and validate cloud networking skills Validate expertise with the AWS Certified Advanced Networking – Specialty exam Visit the advanced networking learning path at aws.amazon.com/training/path-advanced-networking
  19. 19. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
  20. 20. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS manages Customer manages Data source integrations Physical hardware, software, networking, and facilities Provisioning Application code Container orchestration, provisioning Cluster scaling Physical hardware, host OS/kernel, networking, and facilities Application code Data source integrations Security config and updates Network config Management tasks Container orchestration control plane Physical hardware, software, networking, and facilities Application code Data source integrations Work clusters Security config and updates, network config, firewall, and management tasks Physical hardware, software, networking, and facilities Application code Data source integrations Scaling Security config and updates Network config Management tasks Provisioning, managing scaling and patching of servers Serverless operations with AWS Fargate and Lambda AWS Lambda Serverless functions AWS Fargate Serverless containers Amazon ECS/EKS Container-management -as-a-service Amazon EC2 Infrastructure-as-a-service Less More Opinionated
  21. 21. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS manages Customer manages Data source integrations Physical hardware, software, networking, and facilities Provisioning Application code Container orchestration, provisioning Cluster scaling Physical hardware, host OS/kernel, networking, and facilities Application code Data source integrations Security config and updates Network config Management tasks Container orchestration control plane Physical hardware, software, networking, and facilities Application code Data source integrations Work clusters Security config and updates, network config, firewall, and management tasks Physical hardware, software, networking, and facilities Application code Data source integrations Scaling Security config and updates Network config Management tasks Provisioning, managing scaling and patching of servers Serverless operations with AWS Fargate and Lambda AWS Lambda Serverless functions AWS Fargate Serverless containers Amazon ECS/EKS Container-management -as-a-service Amazon EC2 Infrastructure-as-a-service Less More Opinionated
  22. 22. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon EC2 Virtual servers in the cloud Physical servers in AWS global Regions Guest 1 Guest 2 Guest n Hypervisor Host server EC2 instances
  23. 23. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon EC2 instance store Local to instance Nonpersistent data store Data not replicated (by default) No snapshot support SSD or HDD Physical host machine EC2 instances Instance store or
  24. 24. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon EBS EC2 instance EBS volume EBS snapshot gp2 io1 st1 sc1 EBS SSD- backed volumes EBS HDD- backed volumes Amazon S3 Block storage as a service Create, attach, modify through an API Select storage and compute based on your workload Detach and attach between instances Choice of magnetic and SSD-based volume types Supports snapshots: Point-in-time backup of modified volume blocks
  25. 25. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon EC2 14+ years ago… Scale up or down quickly, as needed Pay for what you use “One size fits all” M1
  26. 26. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon EC2 instance characteristics M5d.xlarge Instance family Instance generation Instance size Instance type CPU Memory Storage Network performance Additional capabilities
  27. 27. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Categories Capabilities Options Broadest and deepest platform choice General purpose Burstable Compute intensive Memory intensive Storage (high I/O) Dense storage GPU compute Graphics intensive Amazon Elastic Block Store Amazon Elastic Inference 270+instance types for virtually every workload and business need Choice of processor (AWS, Intel, AMD) Fast processors (up to 4.0 GHz) High-memory footprint (up to 12 TiB) Instance storage (HDD and NVMe) Accelerated computing (GPUs and FPGA) Networking (up to 100 Gbps) Bare metal Size (Nano to 32xlarge) How do you select the right instance to launch and optimize?
  28. 28. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Instance Discovery AWS Compute Optimizer New search and discovery experience to easily find EC2 instance types Quicker and easier for you to find and compare different instance types and project costs Machine learning–based service that recommends optimal AWS resources Recommends optimal EC2 instances and Amazon EC2 Auto Scaling group config Lower costs Optimize performance Get started quickly
  29. 29. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS manages Customer manages Data source integrations Physical hardware, software, networking, and facilities Provisioning Application code Container orchestration, provisioning Cluster scaling Physical hardware, host OS/kernel, networking, and facilities Application code Data source integrations Security config and updates Network config Management tasks Container orchestration control plane Physical hardware, software, networking, and facilities Application code Data source integrations Work clusters Security config and updates, network config, firewall, and management tasks Physical hardware, software, networking, and facilities Application code Data source integrations Scaling Security config and updates Network config Management tasks Provisioning, managing scaling and patching of servers Serverless operations with AWS Fargate and Lambda AWS Lambda Serverless functions AWS Fargate Serverless containers Amazon ECS/EKS Container-management -as-a-service Amazon EC2 Infrastructure-as-a-service Less More Opinionated
  30. 30. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Containers and Docker A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another.1 1 https://www.docker.com/resources/what-container Server Operating System Docker Engine AppA AppB AppC AppD
  31. 31. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon ECS key components Development cluster Container instance Container instance Container instance Productioncluster Container instance Container instance Container instance AmazonElastic Container Service (AmazonECS) Container Container Volume Taskdefinition AmazonElastic Container Registry
  32. 32. ECS agent Docker agent OS Amazon Elastic Compute Cloud (Amazon EC2) instance ECS agent Docker agent OS EC2 instance ECS agent Docker agent OS EC2 instance Amazon Elastic Container Service (Amazon ECS)
  33. 33. Kubectl EKS Architecture
  34. 34. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS manages Customer manages Data source integrations Physical hardware, software, networking, and facilities Provisioning Application code Container orchestration, provisioning Cluster scaling Physical hardware, host OS/kernel, networking, and facilities Application code Data source integrations Security config and updates Network config Management tasks Container orchestration control plane Physical hardware, software, networking, and facilities Application code Data source integrations Work clusters Security config and updates, network config, firewall, and management tasks Physical hardware, software, networking, and facilities Application code Data source integrations Scaling Security config and updates Network config Management tasks Provisioning, managing scaling and patching of servers Serverless operations with AWS Fargate and Lambda AWS Lambda Serverless functions AWS Fargate Serverless containers Amazon ECS/EKS Container-management -as-a-service Amazon EC2 Infrastructure-as-a-service Less More Opinionated
  35. 35. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
  36. 36. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWS manages Customer manages Data source integrations Physical hardware, software, networking, and facilities Provisioning Application code Container orchestration, provisioning Cluster scaling Physical hardware, host OS/kernel, networking, and facilities Application code Data source integrations Security config and updates Network config Management tasks Container orchestration control plane Physical hardware, software, networking, and facilities Application code Data source integrations Work clusters Security config and updates, network config, firewall, and management tasks Physical hardware, software, networking, and facilities Application code Data source integrations Scaling Security config and updates Network config Management tasks Provisioning, managing scaling and patching of servers Serverless operations with AWS Fargate and Lambda AWS Lambda Serverless functions AWS Fargate Serverless containers Amazon ECS/EKS Container-management -as-a-service Amazon EC2 Infrastructure-as-a-service Less More Opinionated
  37. 37. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Anatomy of an AWS Lambda function Handler() function Function to be executed upon invocation Event object Data sent during Lambda function invocation Context object Methods available to interact with runtime information (request ID, log group, more) import json def lambda_handler(event, context): # TODO implement return { 'statusCode': 200, 'body': json.dumps('Hello World!') }
  38. 38. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Serverless applications Event source Function Node.js Python Java C# Go Ruby Powershell Runtime API Changes in data state Requests to endpoints Changes in resource state
  39. 39. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Anatomy of an AWS Lambda function Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Your handler
  40. 40. Anatomy of a Lambda functionImport sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Your handler
  41. 41. Anatomy of a Lambda functionImport sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Your handler Dependencies, configuration information, common helper functions
  42. 42. Anatomy of a Lambda functionImport sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Function Pre-handler-secret-getter() { } Function Pre-handler-db-connect(){ } Your handler Dependencies, configuration information, common helper functions
  43. 43. Anatomy of a Lambda functionImport sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Function Pre-handler-secret-getter() { } Function Pre-handler-db-connect(){ } Function subFunctionA(thing){ ## logic here } Function subFunctionB(thing){ ## logic here } Business logic sub-functions Your handler Dependencies, configuration information, common helper functions Common helper functions
  44. 44. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Anatomy of a serverless application /orders /forums /search /lists /user /... Amazon API Gateway AWS Secrets Manager / Parameter Store Amazon DynamoDB Import sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Function Pre-handler-secret-getter() { } Function Pre-handler-db-connect(){ } Function subFunctionA(thing){ ## logic here } Function subFunctionA(thing){ ## logic here } Dependencies, configuration information, common helper functions Common helper functions Business logic sub-functions Your handler Import sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Function Pre-handler-secret-getter() { } Function Pre-handler-db-connect(){ } Function subFunctionA(thing){ ## logic here } Function subFunctionA(thing){ ## logic here } Dependencies, configuration information, common helper functions Common helper functions Business logic sub-functions Your handler Import sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Function Pre-handler-secret-getter() { } Function Pre-handler-db-connect(){ } Function subFunctionA(thing){ ## logic here } Function subFunctionA(thing){ ## logic here } Dependencies, configuration information, common helper functions Common helper functions Business logic sub-functions Your handler Import sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Function Pre-handler-secret-getter() { } Function Pre-handler-db-connect(){ } Function subFunctionA(thing){ ## logic here } Function subFunctionA(thing){ ## logic here } Dependencies, configuration information, common helper functions Common helper functions Business logic sub-functions Your handler Import sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Function Pre-handler-secret-getter() { } Function Pre-handler-db-connect(){ } Function subFunctionA(thing){ ## logic here } Function subFunctionA(thing){ ## logic here } Dependencies, configuration information, common helper functions Common helper functions Business logic sub-functions Your handler Import sdk Import http-lib Import ham-sandwich Pre-handler-secret-getter() Pre-handler-db-connect() Function myhandler(event, context) { <Event handling logic> { result = SubfunctionA() }else { result = SubfunctionB() return result; } Function Pre-handler-secret-getter() { } Function Pre-handler-db-connect(){ } Function subFunctionA(thing){ ## logic here } Function subFunctionA(thing){ ## logic here } Dependencies, configuration information, common helper functions Common helper functions Business logic sub-functions Your handler
  45. 45. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Learn compute with AWS Training and Certification 20+ free digital courses cover topics related to cloud compute, including introduction to the following services: Resources created by the experts at AWS to help you build cloud compute skills Compute is also covered in the classroom offering, Architecting on AWS, which features AWS expert instructors and hands-on activities • Amazon Elastic Compute Cloud (Amazon EC2) • Amazon EC2 Auto Scaling • AWS Systems Manager • AWS Inferentia and Amazon EC2 Inf1 instances Visit the learning library at https://aws.training
  46. 46. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
  47. 47. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Hardware and software installation Database configuration, patching, and backups Cluster setup and data replication for high availability Capacity planning, and scaling clusters for compute and storage Managing databases on-premises: Time-consuming and complex
  48. 48. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. You You Fully managed services on AWS Spend time innovating and building new applications, not managing infrastructure AWS Self-managed Fully managed Schema design Query construction Query optimization Automatic failover Backup and recovery Isolation and security Industry compliance Push-button scaling Automated patching Advanced monitoring Routine maintenance Built-in best practices
  49. 49. Challenge They experienced service admin challenges with their original provider and wanted to scale business to the next level. Solution They moved from self-managed MySQL to Amazon Aurora MySQL. They use Aurora as the primary transactional database, Amazon DynamoDB for personalized search, and Amazon ElastiCache as in-memory store for sub-millisecond site rendering. Result Initially, the appeal of AWS was the ease of managing and customizing the stack. It was great to be able to ramp up more servers without having to contact anyone and without having minimum usage commitments. AWS is the easy answer for any Internet business that wants to scale to the next level. —Nathan Blecharczyk, Cofounder and CTO of Airbnb “ ” MOVE TO MANAGED → Amazon Aurora Amazon ElastiCache Amazon DynamoDB
  50. 50. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Broad database and analytics services portfolio Relational databases Non-relational databases Data warehouses Hadoop and Spark Amazon Redshift Amazon EMR Operational analytics Amazon Elasticsearch Service Amazon Aurora Amazon DynamoDB Business Intelligence Amazon QuickSight Amazon RDS Amazon DocumentDB Amazon ElastiCache Real-time analytics Amazon Managed Streaming for Apache Kafka PostgreSQL logstash elasticsearch kibana
  51. 51. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Learn databases with AWS Training and Certification 25+ free digital training courses cover topics and services related to relational and nonrelational databases Resources created by the experts at AWS to help you build and validate database skills Validate expertise with the AWS Certified Database – Specialty exam The classroom offering, Planning and Designing Databases on AWS, features AWS expert instructors and hands-on activities Visit the databases learning path at aws.amazon.com/training/path-databases
  52. 52. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon RDS Managed relational database service with a choice of popular databases Easy to administer Easily deploy and maintain hardware, OS, and database software; built-in monitoring Available & durable Automatic Multi-AZ data replication; automated backup, snapshots, and failover Performant & scalable Scale compute and storage with a few clicks; minimal downtime for your application Secure & compliant Data encryption at rest and in transit; industry compliance and assurance programs PostgreSQL
  53. 53. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Amazon Aurora MySQL- and PostgreSQL-compatible relational database built for the cloud Performance and availability of commercial-grade databases at 1/10th the cost Performance and scalability Availability and durability Highly secure Fully managed 5x the throughput of standard MySQL and 3x that of standard PostgreSQL; scale out up to 15 read replicas Fault-tolerant, self-healing storage; six copies of data across three Availability Zones; continuous backup to Amazon S3 Network isolation, encryption at rest/transit, compliance and assurance programs Managed by Amazon RDS: No server provisioning, software patching, setup, configuration, or backups
  54. 54. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Sizing the database
  55. 55. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Storage Block Amazon EBS Amazon FSx for Windows File Server Amazon FSx for Lustre Amazon EFS File Amazon S3 Object
  56. 56. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Providing a fast, durable, highly available, key-based access to objects Amazon S3
  57. 57. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Providing a more reliable, cost-effective, and cloud- native NFS service Amazon EFS
  58. 58. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
  59. 59. Thank you! © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Cobus Bernard Sr Developer Advocate Amazon Web Services @cobusbernard cobusbernard cobusbernard

Hinweis der Redaktion

  • 1/ First, it all starts with our foundation. As you look at the Gartner IaaS MQ, Gartner calls our the breadth of our offering and the strength of our infrastructure, including the unmatched reliability and availability we provide.

    3/ The AWS Cloud spans 69 Availability Zones within 22 geographic Regions around the world, with announced plans for 9 more Availability Zones and four more Regions in, Cape Town, Jakarta, and Milan. global network of 191 Points of Presence (180 Edge Locations and 11 Regional Edge Caches) in 73 cities across 33 countries. 

    4/ Amazon CloudFront uses a global network of 187 Points of Presence (176 Edge Locations and 11 Regional Edge Caches) in 69 cities across 30 countries

    5/ Our AWS geographical regions are comprised of availability zones (AZ’s) that are set of data centers isolated from failures and low latency connectivity providing natively high availability.

    6/ All supported by the AWS global network which connects all of our regions. A network that's been built specifically for the cloud, and we continue to iterate on it.
  • When you configure a VPC, you select an IP address range to use for your virtual network. For IPv4, customers typically use a private address range, as described in RFC 1918. These CIDRs can be as large as /16 (65.6K IPs) or as small as /28 (16 IPs). You then subnet the VPC CIDR for each of the subnets you define.
  • Here we’ve configured 172.31.0.0/16 as the VPC CIDR and created two public subnets (172.31.0.0/24, 172.31.1.0/24) and two private subnets (172.31.128.0/24, 172.31.129.0/24).
  • Here we’ve configured 172.31.0.0/16 as the VPC CIDR and created two public subnets (172.31.0.0/24, 172.31.1.0/24) and two private subnets (172.31.128.0/24, 172.31.129.0/24).
  • Here we’ve configured 172.31.0.0/16 as the VPC CIDR and created two public subnets (172.31.0.0/24, 172.31.1.0/24) and two private subnets (172.31.128.0/24, 172.31.129.0/24).
  • If you’re ready to continue learning, we offer free, digital courses on Networking and Content Delivery, including 2 hour deep dive into AWS Transit Gateway
    Check your knowledge and skills with the one day class on exam readiness for the AWS Certified Advanced Networking – Specialty, available online or in-person.
    Then, validate your experience with an industry-recognized certification AWS Certified Advanced Networking – Specialty.
  • So we talked about ECS, Fargate, and Lambda and so the serverless operations model looks like this

    1/ You can start at the very bottom with EC2 and have access to all the knobs you want to manage or you could go completely serverless with lambda and Fargate where you’re focusing just on your application.

    2/ So the layers of abstractions available to you with AWS is super empowering because your teams have the choice to pick the layer of abstraction they’re most comfortable with and we will provide you the tools, services, and APIs necessary to help you build your application
  • So we talked about ECS, Fargate, and Lambda and so the serverless operations model looks like this

    1/ You can start at the very bottom with EC2 and have access to all the knobs you want to manage or you could go completely serverless with lambda and Fargate where you’re focusing just on your application.

    2/ So the layers of abstractions available to you with AWS is super empowering because your teams have the choice to pick the layer of abstraction they’re most comfortable with and we will provide you the tools, services, and APIs necessary to help you build your application
  • As I mentioned earlier, we EC2 stands for Elastic Compute Cloud.

    We have racks of EC2 servers deployed across all of our regions, with each AWS regions consisting of multiple availability zones or AZs as we call then, and each AZ is typically multiple data centers.

    Within these racks, we have sometimes dozens of servers that each contain Processors, Memory, Networking and sometime local storage. As part of the EC2 stack, we have an hypervisor that partitions these resources, in to virtual machines or guests, which we call as an EC2 instance.
  • Physical disks, local to the physical host hosting your instance
    Non-persistent - only exists for the life of the instance, when you stop/terminate it’s gone. Will survive a reboot
    Data not replicated by default, although you can do that on top of it if you want
    No snapshot support for backups - also DIY
  • EBS is a distributed system.

    Your EBS volume is a logical volume comprised of MANY PHYSICAL DEVICES.

    Because it’s a service distributed across many physical devices, this allows EBS to deliver better performance and durability than if we were simply mapping Volume -> Disk

    Gp2:
    General Purpose SSD

    io1: Provisioned IOPS SSD

    st1: Throughput Optimized HDD

    sc1: Cold HDD



    Snapshots
    First time you take snapshot, every modified block is copied to S3

    Subsequent snapshots are incremental and only changed blocks are backed up

    Deleting a snapshot only removes data exclusive to that snapshot
    Point-in-time backup of modified volume blocks
    Stored in S3, accessed via EBS APIs
    Subsequent snapshots are incremental
    Deleting snapshot will only remove data exclusive to that snapshot
    Crash consistent
  • Back when we launched EC2 in 2006, we offered only 1 instance size. It came with 1 vCPU and 1.7 GB of system memory. Besides giving customers the easy ability to provision compute resources via a web service, there were few other core tenets that really changed the way developers provisioned and consumed compute resources. We allowed customer to only pay for what used and scale up and down quickly as needed. Until EC2, the only option was for customers to build their own data center, procure and manage hardware with long term commitment. What EC2 offered back in 2006 was considered pretty revolutionary.

    The M1 instance that we started offering in 2006 was a good general-purpose instance and addressed the needs of a lot of workloads. Overtime as more customers started using EC2 we got feedback from customers that their particular instance needed a different combination of compute resources than what M1 offered.

    As you might have heard, more than 90% of our product roadmap is influenced by direct customer feedback. Based on this feedback, we have innovated to provide the broadest selection of Compute resources in the market.
  • Show an ec2 instance
  • D – NVE SSD Storage
  • 5/ Let’s start with making it easier to choose the right resources for your workload. With 270+ instances, the #1 question we hear from customers is how do you know which instance to select – which instance type, what size and what attributes do you need to power your workload most efficiently.

    6/ To help address that, I am very excited to announce Mettle.
  • 1/ Previously, you had to reference multiple data sources and test multiple instance types before selecting the best instance type for your workload. You had to repeat this selection process as workloads evolved and new EC2 instance types and features were released.

    2/Now you have a single source of truth for the latest instance types, attributes, regional and zonal offerings, and pricing.

    3/ You can get started by defining your hardware requirements and reviewing the set of instance types which meet these requirements. You can further compare the hardware attributes, pricing, and availability of each instance type if needed. Then you can select and launch an instance, aliased by creating an SSM parameter, or saved in a launch template to be launched later or referenced in existing automation.

    4/ This new experience makes it quicker and easier for us to find and compare different instance types, project costs, and select an instance type that you are confident will give you the performance within budget
  • So we talked about ECS, Fargate, and Lambda and so the serverless operations model looks like this

    1/ You can start at the very bottom with EC2 and have access to all the knobs you want to manage or you could go completely serverless with lambda and Fargate where you’re focusing just on your application.

    2/ So the layers of abstractions available to you with AWS is super empowering because your teams have the choice to pick the layer of abstraction they’re most comfortable with and we will provide you the tools, services, and APIs necessary to help you build your application
  • 1/ And this is what your layers of management end up looking like. You’ve this completely managed orchestration or container management layer but you also have these software management layers just to run your application.

    2/ And all you really want here is to run your containers. And Fargate enables you to do just that. So if you notice here, there is no management of instances, your infra is ready to scale as you application is.

    3/ There are no 2 levels of management of scale anymore. You only define the requirement of your application in terms of a task – how should the service scale, what metrics do you care about and how many more such container or task you want Fargate to launch.
  • So we talked about ECS, Fargate, and Lambda and so the serverless operations model looks like this

    1/ You can start at the very bottom with EC2 and have access to all the knobs you want to manage or you could go completely serverless with lambda and Fargate where you’re focusing just on your application.

    2/ So the layers of abstractions available to you with AWS is super empowering because your teams have the choice to pick the layer of abstraction they’re most comfortable with and we will provide you the tools, services, and APIs necessary to help you build your application
  • 1/ AWS Fargate is a serverless compute engine for containers that works with both Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS).

    2/ Fargate makes it easy for you to focus on building your applications. Fargate removes the need to provision and manage servers, lets you specify and pay for resources per application, and improves security through application isolation by design.
    3/ Fargate allocates the right amount of compute, eliminating the need to choose instances and scale cluster capacity. You only pay for the resources required to run your containers, so there is no over-provisioning and paying for additional servers.

    4/ Fargate runs each task or pod in its own kernel providing the tasks and pods their own isolated compute environment. This enables your application to have workload isolation and improved security by design. This is why customers such as Vanguard, Accenture, Foursquare, and Ancestry have chosen to run their mission critical applications on Fargate.
  • So we talked about ECS, Fargate, and Lambda and so the serverless operations model looks like this

    1/ You can start at the very bottom with EC2 and have access to all the knobs you want to manage or you could go completely serverless with lambda and Fargate where you’re focusing just on your application.

    2/ So the layers of abstractions available to you with AWS is super empowering because your teams have the choice to pick the layer of abstraction they’re most comfortable with and we will provide you the tools, services, and APIs necessary to help you build your application
  • If you’re ready to continue learning, check out our library of free digital courses, including introductory primers on a range of services
    You can also take classroom training to get hands on practice and learn directly from an instructor.
    Visit the learning library for the full list of courses

  • Databases of files
  • For customers running legacy databases on premises, provisioning, operating, scaling, and managing databases is tedious, time-consuming, and expensive. Customer want to spend time innovating and building new applications, and not managing infrastructure.
  • With AWS services, you don’t need to worry about administration tasks such as server provisioning, patching, setup, configuration, backups, or recovery. AWS continuously monitors your clusters to keep your workloads up and running with self-healing storage and automated scaling, so that you can focus on higher value application development. You focus on high value application development tasks such as schema design, query construction & optimization leaving AWS to take care of operational tasks on your behalf.
    You never have to over or under provision infrastructure to accommodate application growth, intermittent spikes, and performance requirements and incur fixed capital costs which include software licensing and support, hardware refresh, and resources to maintain hardware. AWS does it all for you so you can spend time innovating and building new applications, not managing infrastructure.
  • Here’s an example on a customer who’s all-in on AWS. Airbnb moved away for self managing databases to fully managed AWS databases such as Aurora, DynamoDB, and ElastiCache.
    https://aws.amazon.com/solutions/case-studies/airbnb/
    Image source: free stock image from Pexels.com (no license fee)
  • AWS offers the broadest set of databases and analytics services for customers to lift and shift their database and analytics workloads to the cloud. And customers are doing this at record levels across many different areas:
    1/ relational databases – For customers wanting to move away from self-managing Oracle, SQL Server, MySQL, PostgreSQL, and MariaDB databases, AWS offers Amazon RDS and Amazon Aurora.
    2/ non-relational databases – For customers wanting to move away from self-managed non-relational document- and key-value stores such as MongoDB, Redis, and Memcached, AWS offers DynamoDB, DocumentDB and ElastiCache.
    3/ Data Warehouses – customers want to move from their expensive, proprietary Teradata, Oracle and SQL Server Data Warehouses to Amazon Redshift.
    4/ Hadoop and Spark – customers want to move from their Hadoop and Spark deployments on-premises to EMR for cost savings and having a managed service.
    5/ operational analytics – customers want to move from their elasticsearch, logstash, and kibana (ELK) on-premises to Elasticsearch Service for cost savings and having a managed service.
    6/ real-time analytics – customers want to move from their Apache Kafka deployments to Amazon Managed Streaming for Kafka.
  • If you’re ready to continue learning, we offer free digital courses for database services.
    The DATABASE learning path tells you how to get started
    Then, validate your experience with an industry-recognized certification in Databases.
  • Customers that are running commercial databases such as Oracle and SQL Server on premises often choose to first migrate to Amazon RDS, a fully managed relational database service that you can use to run your choice of database engines including open source engines as well as Oracle, and SQL Server. Amazon RDS improves database scale and performance and automates time-consuming administration tasks such as hardware provisioning, database setup, patching, and backups.
  • Amazon Aurora is a MySQL and PostgreSQL-compatible relational database built for the cloud, that combines the performance and availability of traditional enterprise databases with the simplicity and cost-effectiveness of open source databases.
    Amazon Aurora is up to five times faster than standard MySQL databases and three times faster than standard PostgreSQL databases. It provides the security, availability, and reliability of commercial databases at 1/10th the cost. Amazon Aurora is fully managed by Amazon Relational Database Service (RDS), which automates time-consuming administration tasks like hardware provisioning, database setup, patching, and backups.
    Amazon Aurora features a distributed, fault-tolerant, self-healing storage system that auto-scales up to 64TB per database instance. It delivers high performance and availability with up to 15 low-latency read replicas, point-in-time recovery, continuous backup to Amazon S3, and replication across three Availability Zones (AZs).

  • The minimum storage is 10GB. Based on your database usage, your Amazon Aurora storage will automatically grow, up to 64 TB, in 10GB increments with no impact to database performance. There is no need to provision storage in advance.
  • [AWS is successfully in large part due to your input, ideas, and feedback.]

    [Throughout the year, we deliver new or improved capabilities that directly address your input, covering cost-efficiency, higher-availability, integrations across our services, and performance to name a few].

    Based on years of your input and our innovation, AWS has the broadest portfolio of file system services available today.

    And our FS services complement our leadership in both BLOCK and object storage.

    [Lets review a few of the new innovations and capabilities we delivered since last re:Invent]
  • Fast, durable, highly available key-based access to objects
  • [Our 1st file system launched in 2016 was Amazon Elastic File System (EFS).
    Designed to provide a cloud-scale file system for the vast majority of Linux-based workloads. Today EFS serves 100,000’s of customers in 19 AWS regions.]

    We built EFS to be cloud-scale (Elastic), simple (set and forget), cost-effective, performant.

×