Webinar AWS: Desmistificando a Nuvem
•Télécharger en tant que PPTX, PDF•
0 j'aime•250 vues
Apresentação utilizada durante o webinar transmitido em 03/10/2019
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (19)
Similaire à Webinar AWS: Desmistificando a Nuvem
Similaire à Webinar AWS: Desmistificando a Nuvem (20)
Plus de Amazon Web Services LATAM
Plus de Amazon Web Services LATAM (20)
Dernier
Dernier (20)
Webinar AWS: Desmistificando a Nuvem
- 1. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Mv – Marcus Vinicius Ferreira Sr. SA, Public Sector, Education Out/2019 Webinar: Desmistificando a Nuvem Migração, Databases, Storage
- 2. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Mv – Marcus Vinicius Ferreira mvferr@amazon.com Solutions Architect BR, Public Sector, Education Presenter Mv
- 3. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Agenda: Desmistificando a Nuvem • Migração • Storage • Databases • Q&A
- 4. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Migração
- 5. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Migration process Portfolio Discovery & Planning Operate & Optimize Migration Preparation & Business Case Application Design, Migration & Validation
- 6. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. AWS Application Discovery Service (AWS ADS) Agents (Windows/ Linux) Data Center Encrypted data Capture and visualize system inventory, performance, and dependencies AWS Application Discovery Service Import from existing sources Discovery Connector (vCenter) Capture Analyze Discovery Data Estimate EC2 Costs
- 7. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Analysis … What Should We Look For? Apps, Servers, Connections No. of apps and servers Application and server dependencies Performance metrics Allocate and right-size target resources Service naming, tagging Identify patterns Group servers and applications
- 8. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. AWS Migration Hub Discover usingAWSADS or Import discovery data from existing sources Track the migration status of your applications across multiple tools in one place Use the migration tools that best fit your needs – AWS or Partner tools integrated Available to all AWS customers at no additional charge
- 9. Example Data Center: Where Do We Put All of This on AWS? DB (Master) DB (Slave) Back-ups on tapes Web server Web server App serverApp server App server SAN NAS file server File system disks LDAP server
- 10. Example Data Center: Where Do We Put All of This on AWS? Web server Web server App serverApp server App server Amazon Elastic File System Elastic Load Balancing Elastic Load Balancing Amazon Elastic Block Store Amazon RDS (Master) Amazon RDS (Standby) Backups to Amazon S3 or Glacier AWS Directory Service
- 11. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Tamanhos de Instâncias ≈ ≈ ≈ 1 x 1 2 x 1/2 4 x 1/4 8 x 1/8 ~$1.60 ~$0.80 ~$0.40 ~$0.20
- 12. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Storage
- 13. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Block vs File vs Object Block Storage Raw Storage Data organized as an array of unrelated blocks Host File System places data on disk e.g.: Microsoft NTFS, Unix ZFS File Storage Unrelated data blocks managed by a file (serving) system Native file system places data on disk Object Storage Stores Virtual containers that encapsulate the data, data attributes, metadata and Object IDs API Access to data Metadata Driven, Policy-based, etc
- 14. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Three types of storage File ObjectBlock Amazon EFS Amazon FSx Amazon EBS Amazon S3, Amazon Glacier
- 15. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Performance comparison of storage types File Object Block Latency Throughput
- 16. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Object storage S3 Standard S3 Glacier Deep Archive S3 Glacier S3 Intelligent-Tiering S3 One Zone-IA S3 Standard-IA Block storage Provisioned IOPS SSD Cold HDD Throughput-Optimized HDD NEW! COMING SOON! File storage EFS Standard EFS Infrequent Access COMING SOON! Elastic Amazon EFS Amazon S3 Amazon EBS Amazon EC2
- 17. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. AWS block storage offerings EC2 instance store sc1st1 io1gp2 EBS SSD-backed volumes EBS HDD-backed volumes HDDSSD
- 18. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. EBS volume types HDDSSD Provisioned IOPS SSD io1 General Purpose SSD gp2 Throughput Optimized HDD st1 sc1 Cold HDD
- 19. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. or Choosing an EBS volume type What is more important to your workload? IOPS Throughput? HDDSSD
- 20. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. i3 gp2 Choosing an EBS volume type Latency? < 1 ms Single-digit ms Which is more important? Cost Performance IOPS ≤ 80,000> 80,000 is more important
- 21. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. i3 gp2 io1 Choosing an EBS volume type Latency? < 1 ms Single-digit ms Which is more important? Cost Performance IOPS ≤ 80,000> 80,000 is more important
- 22. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. i3 gp2 io1 Choosing an EBS volume type Latency? < 1 ms Single-digit ms Which is more important? Cost Performance IOPS ≤ 80,000> 80,000 is more important Throughput?
- 23. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Throughput is more important Small, random I/O Large, sequential I/O i3 gp2 io1 st1 d2 Choosing an EBS volume type Latency? < 1 ms Single-digit ms ≤ 1,750 MiB/s Aggregate throughput? > 1,750 MiB/s Which is more important? Cost Performance IOPS ≤ 80,000> 80,000 is more important Which is more important? Cost Performance
- 24. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Throughput is more important Small, random I/O Large, sequential I/O i3 gp2 io1 sc1 st1 d2 Choosing an EBS volume type Latency? < 1 ms Single-digit ms ≤ 1,750 MiB/s Aggregate throughput? > 1,750 MiB/s Which is more important? Cost Performance IOPS ≤ 80,000> 80,000 is more important Which is more important? Cost Performance
- 25. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Throughput is more important Small, random I/O Large, sequential I/O i3 gp2 io1 sc1 st1 d2 Choosing an EBS volume type Latency? < 1 ms Single-digit ms ≤ 1,750 MiB/s Aggregate throughput? > 1,750 MiB/s Which is more important? Cost Performance IOPS ≤ 80,000> 80,000 is more important Which is more important? Cost Performance
- 26. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Don’t know Choosing an EBS volume type your workload yet?
- 27. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. EBS volume types: General Purpose SSD gp2 Throughput: Up to 160 MiB/s Latency: Single-digit ms Capacity: 1 GiB to 16 TiB Baseline: 100 to 10,000 IOPS; 3 IOPS per GiB Burst: 3,000 IOPS (for volumes up to 1,000 GiB) Great for boot volumes, low-latency applications, and bursty databases General Purpose SSD
- 28. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. EBS: Monitoring
- 29. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. EBS: Elastic Block Storage EBS volume EC2 instance • Block storage as a service • Create, attach volumes through an API • Service accessed over the network
- 30. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. EBS: Elastic Block Storage EBS volume Availability Zone AWS Region EC2 instance • Volume and instance must be in the same AZ
- 31. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. EFS: a shared filesystem via NFS NFS Clients NFS Clients NFS Clients Mount Target NFS mount point Mount Target Mount Target
- 32. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. ObjectKeys An object key is the unique identifier for an object in a bucket. http://doc.s3.amazonaws.com/2006-03-01/AmazonS3.html Bucket Object/Key
- 33. Amazon S3: HTTP access 1. HTTP/HTTPS access 2. Unlimited amount of files 3. Unlimited growth... 4. Any type of data: backups, photos, videos, documents, logs 5. Cheap, unlimited storage [bucket name] Preview2.mp4 Tokyo Region (ap-northeast-1) Bucket Object https://s3-ap-northeast-1.amazonaws.com/[bucket name]/Preview2.mp4 https://s3-ap-northeast-1.amazonaws.com/[bucket name]/ Region code Bucket name Key
- 34. A Closer Look: S3 Durability 4 9s durability 5 9s durability S3, S3-IA Glacier 11 9s durability 99.999999999 % VS.
- 35. VS. Understanding Durability designed for 99.99% durability Two copies on one site designed for 99.999% durability Copies on two sites designed for 99.999999999% durability GlacierStandard IA AWS Region
- 36. S3 Standard S3 Standard – Infrequent Access Amazon Glacier Active data Archive dataInfrequently accessed data Milliseconds Minutes to HoursMilliseconds $0.021/GB/mo $0.004/GB/mo$0.0125/GB/mo Choice of storage classes on Amazon S3
- 37. S3: Sharing web files 172.31.0.0/16 sa-east-1a sa-east-1b sa-east-1c
- 39. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Databases: Amazon RDS
- 40. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Corporate data center Database DB on EC2 instance RDS
- 41. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Databases: SQL, NoSQL EC2 Server Volume Volume Volume Volume Volume Volume
- 42. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Amazon Relational Database Service • Introduced in 2009 • Multi-engine support: Amazon Aurora, MySQL, MariaDB, PostgreSQL, Oracle, Microsoft SQL Server • Automated provisioning, patching, scaling, replicas, backup/restore, monitoring, failover • Easy to manage via console or API • Low-cost ‘pay for what you use’ • Built-in High availability with RDS Multi-AZ and Amazon Aurora
- 43. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Commercial Open source Cloud native MySQL Compatible PostgreSQL Compatible Amazon Aurora
- 44. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. If you choose a managed database service Power, HVAC, net Rack and stack Server maintenance OS patches DB s/w patches Database backups App optimization High availability DB s/w installs OS installation Scaling Database tuning Design and Review App optimization Best practices you
- 45. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Amazon RDS Performance Insights DB Load : Average Active Sessions • Easy • Powerful • Identifies database bottlenecks Top SQL • Identifies source of bottleneck Enables Problem Discovery • Adjustable Time frame • Hour, day, week and longer • Investigate: SQL, waits, user, hosts
- 46. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Automated backups Point-in-time recovery for your DB instance • Scheduled daily volume backup of entire instance • Archive database change logs • 35–day maximum retention • Minimal impact on database performance • Taken from standby when running Multi-AZ Every day during your backup window, RDS creates a storage volume snapshot of your instance Every five minutes, RDS backs up the transaction logs of your database
- 47. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Database snapshots Backups of your entire DB instance in Amazon S3 Bucket Volume Snapshot 2Snapshot 1 Snapshot 3 • Always incremental • Amazon S3 99.999999999% durability • Supports encryption • Copy across accounts, across regions
- 48. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Tamanhos de Instâncias RDS 1 x 1 2 x 1/2 ≈ 4 x 1/4 ≈ 8 x 1/8 ≈
- 49. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Database Resize Availability Zone 10.1.1.0/24 Prod
- 50. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Database Resize... and separation. Availability Zone 10.1.1.0/24 ERP Website 1 Website 2
- 51. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Simple and fast compute scaling on Amazon RDS
- 52. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Scaling Instances Up/Down AWS Management Console
- 53. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Amazon CloudWatch for RDS CPU utilization Storage Memory 50+ system/OS metrics 1–60 second granularity DB connections Selects per second Latency (read and write) Cache hit ratio Replica lag CloudWatch alarms Similar to on-premises custom monitoring tools
- 54. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Database Resize... and separation. Availability Zone AWS Region 10.1.2.0/24 Availability Zone 10.1.1.0/24 ERP Website 1 Website 2 ERP Website 1 Website 2
- 55. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Availability Zone A AWS Region 10.1.0.0/16 10.1.1.0/24 Availability Zone B 10.1.2.0/24 Synchronous Replication M S Single Availability Zone Configuration HA Multi Availability Zone Configuration
- 56. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. High availability—Multi-AZ to DNS Availability Zone A AWS Region Availability Zone B M S DNS mydatabase.us-west-2.rds.amazonaws.com:3306 M
- 57. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. High availability—Multi-AZ to DNS Availability Zone A AWS Region Availability Zone B DNS mydatabase.us-west-2.rds.amazonaws.com:3306 MMS
- 58. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. RDS Multi-AZ: High-Availability comes FIRST. 172.31.0.0/16 sa-east-1a sa-east-1b sa-east-1c
- 59. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Database Resize... and separation. Availability Zone AWS Region 10.1.2.0/24 Availability Zone 10.1.1.0/24 ERP Website 1 Website 2 ERP Website 1 Website 2
- 60. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Database Resize... and separation. Availability Zone AWS Region 10.1.2.0/24 Availability Zone 10.1.1.0/24 ERP Website 1 Website 2 ERP Website 1 Website 2
- 61. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Read Replicas Read scaling and disaster recovery RDS for MySQL, PostgreSQL, MariaDB • Relieve pressure on your master node with additional read capacity • Bring data close to your applications in different regions • Promote a read replica to a master for faster recovery in the event of disaster Asynchronous replication BI/reporting application server Read only Read/write Primary Read replica Slave
- 62. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Database Resize... and separation. Availability Zone AWS Region 10.1.2.0/24 Availability Zone 10.1.1.0/24 ERP Website 1 Website 2 ERP Website 1 Website 2
- 63. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Database: RDS Aurora
- 64. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Amazon Aurora Storage Engine Overview AZ 1 AZ 2 AZ 3
- 65. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Amazon Aurora Storage Engine Overview AZ 1 AZ 2 AZ 3 Storage Node Storage Node Storage Node Storage Node Storage Node Storage Node Storage Monitoring
- 66. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Amazon Aurora Storage Engine Overview Data is replicated 6 times across 3 Availability Zones Continuous backup to Amazon S3 (built for 11 9s durability) Continuous monitorig of nodes and disks for repair 10 GB segments as unit of repair or hotspot rebalance Quorum system for read/write; latency tolerant Quorum membership changes do not stall writes Storage volume automatically grows up to 64 TB AZ 1 AZ 2 AZ 3 Amazon S3 Database Node Storage Node Storage Node Storage Node Storage Node Storage Node Storage Node Storage Monitoring
- 67. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Simplify storage management • Automatic storage scaling up to 64 TB—no performance impact • Continuous, incremental backups to Amazon S3 • Instantly create user snapshots—no performance impact • Automatic restriping, mirror repair, hot spot management, encryption Up to 64 TB of storage—autoincremented in 10 GB units up to 64 TB
- 68. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. BETTER DURABILITY: Aurora 6-way replicated storageSix copies across three Availability Zones • 4 out of 6 write quorum; 3 out of 6 read quorum • Peer-to-peer replication for repairs AZ 1 AZ 2 AZ 3 AZ 1 AZ 2 AZ 3 Read availabilityRead and write availability
- 69. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. FAST: Aurora MySQL – 5x Read/Write Throughput WRITE PERFORMANCE READ PERFORMANCE MySQL SysBench results R3.8XL: 32 cores / 244 GB RAM Five times higher throughput than stock MySQL based on industry standard benchmarks. 0 25,000 50,000 75,000 100,000 125,000 150,000 0 100,000 200,000 300,000 400,000 500,000 600,000 700,000 Aurora MySQL 5.6 MySQL 5.7
- 70. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. DMS
- 71. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Databases:dump,load Dump -> Load
- 72. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWSDatabaseMigrationService(DMS) Migrate • Migrate business-critical applications • Migrate data warehouse to Redshift • Upgrade to a minor version • Consolidate shards into Aurora • Archive old data • Migrate from NoSQL to SQL, SQL to NoSQL or NoSQL to NoSQL Amazon RDS Amazon Redshift Amazon Aurora Amazon DynamoDB Amazon S3
- 73. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. AWSDatabaseMigrationService(DMS) Replicate • Create cross region Read Replicas • Run your analytics in the cloud • Populate your data lake
- 74. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. AWS Database Migration Service Accelerate Migrations to Amazon Redshift DMS usage is free for 6 months For more information: https://aws.amazon.com/dms/free-dms/ “AWS Database Migration Service is the most impressive migration service we’ve seen.” Azure SQL Database AWS DMS RDS / Aurora 2. Relational Databases 1. Non-Relational Databases 3. Other sources Amazon S3
- 75. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Questions?
- 76. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. ThankYou! https://aws.amazon.com/
- 77. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Pesquisa: ganhe US$30! http://bit.ly/techtalkspesquisa
- 78. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. AWS Global Infrastructure 18 Regions – 55 Availability Zones – 114 Edge Locations Region & Number of Availability Zones AWS GovCloud (2) EU Ireland (3) US West Frankfurt (2) Oregon (3) London (2) Northern California (3) Asia Pacific US East Singapore (2) N. Virginia (5), Ohio (3) Sydney (2), Tokyo (3), Seoul (2), Mumbai (2) Canada Central (2) China Beijing (2) South America São Paulo (3) Announced Regions Paris, Ningxia
- 79. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Region New Region Coming Soon Edge Location Region & Number of Availability Zones# The Global Infrastructure
- 80. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved. REGION ~ 2ms latency AZa AZc AZb Redundant Tier-1 Internet & Inter-Region Connectivity TCTC DC DC DC DC DCDC DC DC DC
Notes de l'éditeur
- [Migration process] In any migration project to AWS, there are four phases that all customers go through in order to be successful and derive optimal value from their migration to the cloud. First, you must do migration preparation including doing an initial portfolio analysis to build a directional business case for migration. We also suggest to start with a Migration Readiness Assessment to understand your readiness to migrate to the cloud at scale. Next, a detailed portfolio discovery of all in-scope IT assets needs to be performed to obtain the data necessary to create a migration plan for assets to be migrated. This plan determines the migration strategy and waves of the applications targeted for AWS. The detailed discovery data is also used to further refine the business case. After migration planning is completed, the actual execution of the migration takes place in which applications are designed, migrated, and validated. And finally, once the applications are in AWS, you have to operate the applications in the cloud, including going through an optimization phase to maximize the benefits derived from hosting applications in AWS. Optimizing activities can address cost, performance, security or resiliency concerns for a specific application stack. The discussion today focuses on the first three phases of this process - let’s look at some of the common challenges we see experienced by migration customers…
- [AWS Application Discovery Service] Application Discovery Service is a discovery tool that captures details of your on-premises infrastructure including server details such as OS name, ip addresses, mac address and time series utilization data such as CPU utilization, memory utilization, and IOPS throughput. In addition, it also captures the network connections and process information. You can further analyze the captured information to evaluate the cost of migration to AWS to plan migration. Application Discovery Service supports three ways to collect data: Agent-based discovery can be performed on any given virtual machine or physical server that is part of your on-premises environment (Windows or Linux). The agent is deployed on each virtual machine or physical server separately and runs only in the user space. The Agent supports all major Linux versions such as Red Hat, CentOS, Ubuntu etc. and Windows Server versions such as 2003, 2008, 2012 etc. Agentless Discovery Connector designed for VMware environment that is used by deploying an OVA file on a VMware host that allows it to collect data from each VM server. Agentless discovery process is OS agnostic and is able to read data for any VM irrespective of the OS. Agentless discovery does collect less information than Agent-based collection, however. Import from existing data sources – You are also able to import data that you may already have (such as data from your CMDB or ServiceNow data) or that you may have already collected using a partner tool (such as RISC Networks). Data from all of the sources is visible directly in AWS Migration Hub console, as well as, via an API or an export file. Right-sizing your compute resources is one dimension of understanding your total cost of ownership (TCO). Use the EC2 instance recommendation feature of Migration Hub when you want an understanding of your projected EC2 costs. We also offer a more detailed assessment, including optimizations for Microsoft licensing and storage costs, using TSO Logic For data collected with Agent-based discovery, data can be automatically exported to directly to Amazon Athena where it may be queried directly or visualized using Amazon QuickSight. Using Amazon QuickSight provides you the flexibility to analyze the data to view the network dependencies between servers and identify the processes that are running on a given server (we will talk more about this later).
- From the vast amount of portfolio data collected, we extract key pieces of information to form a migration plan. Connections is a critical piece. It helps determine application and server dependencies and also help identify access patterns. Performance metrics is another factor to help right size resources in the cloud. Another aspect is using service naming conventions, tags and other host metadata to help identify patterns and group servers and applications for migration. The portfolio discovery process shall aim at completeness and usability. If additional data are required, you need to determine tools and actions to complete discovery.
- [AWS Migration Hub] AWS Migration Hub is designed to be a single location to track the progress of application migrations across AWS and partner solutions. With AWS Migration Hub, you can discover your on-premise portfolio using AWS Application Discovery Service and/or import discovery data from existing sources (such as your CMDB) or from other discovery tools. You can view sever information and group servers into applications to help plan your migration. You can track the progress of your migration using the migration tools that best fit your needs (AWS and AWS partner). AWS Migration Hub can manage migrations in any AWS Region that has the necessary migration tools available. AWS Migration Hub itself runs in the US West (Oregon) Region. Migration Hub is available to all AWS customers at no additional charge. You only pay for the cost of the migration tools you use, and any resources being consumed on AWS.
- A traditional on-premises or data center–based infrastructure might include a setup like this. Here we'll walk you through just one example of how an arrangement like this could be set up and run on AWS instead.
- What happens when you turn this data center infrastructure into an AWS infrastructure? Servers, such as these web servers and app servers, are replaced with Amazon EC2 instances that run all of the same software. Because Amazon EC2 instances can run a variety of Windows Server, Red Hat, SUSE, Ubuntu, or our own Amazon Linux operating systems, virtually all server applications can be run on Amazon EC2 instances. The LDAP server is replaced with AWS Directory Service, which supports LDAP authentication and allows you to easily set up and run Microsoft Active Directory in the cloud or connect your AWS resources with existing on-premises Microsoft Active Directory. Software-based load balancers are replaced with Elastic Load Balancing load balancers. Elastic Load Balancing is a fully managed load balancing solution that scales automatically as needed and can perform health checks on attached resources, thus redistributing load away from unhealthy resources as necessary. SAN solutions can be replaced with Amazon Elastic Block Store (EBS) volumes. These volumes can be attached to the application servers to store data long-term and share the data between instances. Amazon Elastic File System (EFS), currently available via preview, could be used to replace your NAS file server. Amazon EFS is a file storage service for Amazon EC2 instances with a simple interface that allows you to create and configure file systems. It also grows and shrinks your storage automatically as you add and remove files, so you are always using exactly the amount of storage you need. Another solution could be to run an NAS solution on an Amazon EC2 instance. Many NAS solutions are available via the AWS Marketplace at https://aws.amazon.com/marketplace/. Databases can be replaced with Amazon Relational Database Service (RDS), which lets you run Amazon Aurora, PostgreSQL, MySQL, MariaDB, Oracle, and Microsoft SQL Server on a managed AWS-based platform. Amazon RDS offers master, read replica, and standby instances. Finally, Amazon RDS instances can be automatically backed up to Amazon S3, thus replacing the need for on-premises database backup hardware.
- Notes: Ou seja, uma reserva de c5.4xlarge fornece 720 horas mensais desse tamanho, ou 1440 horas de 2xlarge, ou 360 de 8.xlarge
- Each storage option has a unique combination of performance, durability, cost, and interface
- What is EBS? Create a volume, attach to an EC server. That’s it.
- What is EBS? Create a volume, attach to an EC server. That’s it.
- EBS volumes are bound to an AZ. Restriction number 1.
- EFS....! EFS is a shared volume service, based on the NFS protocol.
- Because the combination of a bucket, key, and version ID uniquely identifies each object, Amazon S3 can be thought of as a basic data map between "bucket + key + version" and the object itself. Every object in Amazon S3 can be uniquely addressed through the combination of the web service endpoint, bucket name, key, and optionally, a version. For example, in the URL http://doc.s3.amazonaws.com/2006-03-01/AmazonS3.html, "doc" is the name of the bucket and "2006-03-01/AmazonS3.html" is the key.
- S3 is great. Unlimited storage, with a very low cost. But it is accessible via HTTP/HTTPS mainly.
- Across the board, S3, SIA and Glacier all offer the same 11 9’s durability, where AWS stores data redundantly across multiple facilities and storage devices, and the services automatically perform data integrity check in the background to guard against potential data corruption. I work with many customers who archive data by storing two copies of tape either in the same building or one copy on-site and one remote. When we discuss durability, which is a big deal for many archive customers, many are accustomed to thinking in number of “copies” and found the 11 9’s a bit non-intuitive. To bridge that, we did a thought experiment with a large studio where, at a high level, we walked them through how we derived the 11 9’s using a Markov chain model where we modeled failures from storage device, server, network, availability zone, etc. We asked them to estimate their two-copy tape durability using a similar concept and they estimated ~4 9’s for two copies in a single building or ~5 9’s for two copies in separate locations. This helped them realize that Glacier’s 11 9’s durability can be thought of as 6 to 7 orders of magnitude more durable than two copies of tape and helped us bridge the conversation.
- Across the board, S3, SIA and Glacier all offer the same 11 9’s durability, where AWS stores data redundantly across multiple facilities and storage devices, and the services automatically perform data integrity check in the background to guard against potential data corruption. I work with many customers who archive data by storing two copies of tape either in the same building or one copy on-site and one remote. When we discuss durability, which is a big deal for many archive customers, many are accustomed to thinking in number of “copies” and found the 11 9’s a bit non-intuitive. To bridge that, we did a thought experiment with a large studio where, at a high level, we walked them through how we derived the 11 9’s using a Markov chain model where we modeled failures from storage device, server, network, availability zone, etc. We asked them to estimate their two-copy tape durability using a similar concept and they estimated ~4 9’s for two copies in a single building or ~5 9’s for two copies in separate locations. This helped them realize that Glacier’s 11 9’s durability can be thought of as 6 to 7 orders of magnitude more durable than two copies of tape and helped us bridge the conversation.
- When you view our object storage as a portfolio of storage classes, we provide 3 storage options with different performance characteristics and price points. S3 Standard which is our high performance object storage - very active, hot workloads. available in milliseconds starts at 2.1 cents/GB/month depending on the region S3 Standard - Infrequent Access shares the same millisecond access times as S3 Standard, but designed for data you plan to access maybe a few times a year or what we think of as “active archive”. S3-IA costs $0.0125/GB/mo, and then you pay a nominal fee for requests. Glacier is that cold archival tier access latency from minutes to hours, depending on the retrieval option you choose, storage costs $0.004/GB/month.
- EBS disks can be attached to RDS DB servers or EC2 servers. Keep in mind that EC2 auto-scaling machines will die and their disks will be lost. Any information that must be saved is better placed in a database table or S3 bucket. EBS disks attached to a database server are permanent. But even so, a database backup is always needed for production systems.
- For those legacy systems that are not auto-scaling friendly, and must write information to local disks without loosing it, EFS is the solution. Any generated information can be saved to a database table, a S3 bucket, or a EFS share.
- Many of you have applications…
- Databases – any type of them – want big and fast disks. EBS is the case. Observation: EFS is not a database friendly solution.
- Based on our experiences running the databases behind Amazon.com, We introduced Amazon RDS to help customers run their relational databases. Lower TCO because we manage “the muck” Get more leverage from your teams Focus on the things that differentiate you Built-in high availability and cross region replication across multiple data centers Available on all engines, including base/standard editions, not just for enterprise editions Now even a small startup can leverage multiple data centers to design highly available apps with over 99.95% availability.
- There are lots of different choices for your database engine on RDS. Each of these engines operate differently, offer different functionality, and have different licensing requirements. Everyone has their favorite engine and they use them for specific purposes. On the commercial side we have Oracle and Microsoft SQL Server On the open source side we have MySQL, PostgreSQL, and MariaDB And in its own category we have Amazon Aurora which is a My SQL compatible relational database built to take advantage of many of the properties that exist with modern cloud computing. Relational databases have existed … but standard relational technology is not the best fit for cloud platforms – hence Aurora – we also kept in mind opensource and compatibility, easy for customers to mograte – hence MySQL and now Postgres compatibility -------- MariaDB - https://en.wikipedia.org/wiki/MariaDB MariaDB – Fork of the MySQL database. Led by the original developers of MySQL after concerns when it was acquired by Oracle and that the project might become a closed project. Works to maintain high compatibly with MySQL. Also has features to support non-blocking operations and progress reporting.
- Talk Track: Together with the new edition of Amazon Aurora we are also announcing a new database monitoring feature called Performance Insights. Performance Insights is designed to help customers quickly assess whether there are any performance bottlenecks in their relational database workloads and where to take action. Performance Insights collects detailed database performance data through light weight mechanisms and uses the data to drive an intuitive graphical interface that provides a simple and complete view of recent database performance. Performance Insights is the answer: Let’s you see your overall instance load Drill down by SQL Statement, by time, or by calling host. For questions: Roadmap: will be rolling out incrementally to all RDS engines over 2018 First release will be on Postgres compatible edition of Aurora followed by the MySQL compatible just after re:Invent Q1 will introduce support for Mysql, MariaDB and Postgres Q2 will introduce support for SQL Server and Oracle See the preview in the demo grounds Feature is free. Will be supported on all instances except micros
- Notes: Ou seja, uma reserva de c5.4xlarge fornece 720 horas mensais desse tamanho, ou 1440 horas de 2xlarge, ou 360 de 8.xlarge
- The computation and memory capacity of a DB instance is determined by its DB instance class. You can change the CPU and memory available to a DB instance by changing its DB instance class; to change the DB instance class, you must modify the DB instance. Here are the DB instance classes available through Amazon RDS: Micro instances (db.t1.micro): An instance sufficient for testing but should not be used for production applications. Standard - Current Generation (m3): Second generation instances that provide more computing capacity than the first generation db.m1 instance classes at a lower price. Memory Optimized - Current Generation (db.r3): Second generation instances that provide memory optimization and more computing capacity than the first generation db.m2 instance classes at a lower price. Burst Capable - Current Generation (db.t2): Instances that provide baseline performance level with the ability to burst to full CPU usage. You can change from one database instance type to another. There will be a brief availability event during the changeover. You can increase the amount of storage available to your database instance on demand for the MySQL, Oracle, and PostgreSQL database engines. This change is performed online, without an availability impact. Amazon Aurora automatically grows the database size on demand.
- Compute scaling in Aurora is by creating a new read replica, and do a failover - can be done in 10-15 seconds versus a host replacement type operations which is a few minutes Aurora storage volume is 10GB and we do auto scaling, Let’s take some time to dive deeper into a particular use case around scaling the database master instance. Here is a quick example of what it would take to scale your RDS database instance up or down. Here we have screen shots of what you do when you want to change the instance size. Choose the Modify option from the Instance Actions menu of the RDS console. Then choose what you want your new DB Instance Class to be. Finally, determine if you want to apply the change immediately or not. If you do not apply the change immediately then the change will be scheduled to occur during the preferred maintenance window that you defined when creating the database. Keep in mind that when you are applying the change immediately you could incur some downtime as the instance size is changed so be aware of what your applications that are accessing the database can tolerate in regards to downtime. http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.DBInstance.Modifying.html
- 6 COPIES – 6 copies but actually LESS WRITES Backup – no WINDOWS or IMPACT Monitoring Quorum – 4/6 = COMMITTED transaction MEMBERSHIP changes (upgrades/repairs) Storage GROWS automatically ---- (1 minute) The Amazon Aurora Storage Engine duplicates data 6 times across 3 Availability Zones. By the way, that sound like a lot of writes – but remember that no data blocks are ever written (only log records) – so it ends up being LESS data being written, by far. I’ll get into that a little bit more later. Data is continually backed up to S3. No backup windows. No performance impact during backup. The system has a separate Monitoring and Management layer you’ll never see as a customer. To you, the databases just keeps running. Aurora has a quorum algorithm for writes – as soon as 4 of the 6 writes are durable, the system successfully returns a committed transaction to the database. This means that lagging disks/nodes/even AZ’s can be ridden through by the system with little or no impact on performance. Another key benefit of a quorum-based system is that nodes can leave and join the system as they are upgraded or repaired and there is absolutely no performance or availability impact. Also, storage grows automatically in 10 GB increments as DB size grows – up to 64 TB.
- 6 COPIES – 6 copies but actually LESS WRITES Backup – no WINDOWS or IMPACT Monitoring Quorum – 4/6 = COMMITTED transaction MEMBERSHIP changes (upgrades/repairs) Storage GROWS automatically ---- (1 minute) The Amazon Aurora Storage Engine duplicates data 6 times across 3 Availability Zones. By the way, that sound like a lot of writes – but remember that no data blocks are ever written (only log records) – so it ends up being LESS data being written, by far. I’ll get into that a little bit more later. Data is continually backed up to S3. No backup windows. No performance impact during backup. The system has a separate Monitoring and Management layer you’ll never see as a customer. To you, the databases just keeps running. Aurora has a quorum algorithm for writes – as soon as 4 of the 6 writes are durable, the system successfully returns a committed transaction to the database. This means that lagging disks/nodes/even AZ’s can be ridden through by the system with little or no impact on performance. Another key benefit of a quorum-based system is that nodes can leave and join the system as they are upgraded or repaired and there is absolutely no performance or availability impact. Also, storage grows automatically in 10 GB increments as DB size grows – up to 64 TB.
- 6 COPIES – 6 copies but actually LESS WRITES Backup – no WINDOWS or IMPACT Monitoring Quorum – 4/6 = COMMITTED transaction MEMBERSHIP changes (upgrades/repairs) Storage GROWS automatically ---- (1 minute) The Amazon Aurora Storage Engine duplicates data 6 times across 3 Availability Zones. By the way, that sound like a lot of writes – but remember that no data blocks are ever written (only log records) – so it ends up being LESS data being written, by far. I’ll get into that a little bit more later. Data is continually backed up to S3. No backup windows. No performance impact during backup. The system has a separate Monitoring and Management layer you’ll never see as a customer. To you, the databases just keeps running. Aurora has a quorum algorithm for writes – as soon as 4 of the 6 writes are durable, the system successfully returns a committed transaction to the database. This means that lagging disks/nodes/even AZ’s can be ridden through by the system with little or no impact on performance. Another key benefit of a quorum-based system is that nodes can leave and join the system as they are upgraded or repaired and there is absolutely no performance or availability impact. Also, storage grows automatically in 10 GB increments as DB size grows – up to 64 TB.
- Storage management is tedious task with traditional databases…. Taking and managing database backups is another challenge with traditional databases… But if you are doing an application release and you want to click a button ….
- Walk through from data inputs on the left (properties, agents, and buyer information and activities) to how the data is streamed and processed, and finally the insights.
- Walk through from data inputs on the left (properties, agents, and buyer information and activities) to how the data is streamed and processed, and finally the insights.
- We designed AWS Database Migration Service (DMS) to be simple - you can get started in less than ten minutes. We designed it to enable near-zero-downtime migration. And we designed it to be a kind of replication Swiss army knife to replicate data between on-premises systems, RDS, EC2, and across database engine type. We have completed over 1,000 unique migrations to Redshift using DMS. AWS Database Migration Service (DMS) easily and securely migrates and/or replicate your databases and data warehouses to AWS AWS Schema Conversion Tool (SCT) converts your commercial database and data warehouse schemas to open-source engines or AWS-native services, such as Amazon Aurora and Redshift The real power of the solution becomes apparent when you realize that you can move between database engines or between data warehouses, enabling you to move away from expensive, commercial databases, to cloud-native, open source solutions. And don’t worry, at AWS we don’t believe in vendor lock-in. You can use DMS just as easily to move data out of the cloud as into it.
- AWS serves hundreds of thousands of customers in more than 190 countries. Amazon CloudFront and Amazon Route 53 services are offered at AWS Edge Locations
- Each AZ is placed in a way to ensure that latency is as low as 2 ms 99% of the time.