Amazon Aurora is a fully managed MySQL-compatible database with high-end commercial database features and performance at one-tenth the cost. Since launching Aurora a year ago we have added many new capabilities and features. Some of these features include  encryption,  database snapshot sharing, enhanced monitoring, cross-region replication, S3 binary snapshot ingestion and customized failover priority.  In this session we'll demonstrate how these features work and discuss how you can make the best use of them. Learning Objectives: • Learn about the newly added features of Aurora • Learn how to use those features • Learn when and why to use those features Who Should Attend: • IT Managers, DBAs, Enterprise and Solution Architects, Devops Engineers and Developers

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Steve Abraham – Solutions Architect
September 28, 2016
Amazon Aurora
New Features

2. Options for hosting databases
Self-managed EC2 instances Fully managed
Corporate data
center
Database DB on EC2
instance RDS

3. If You Host Your Databases On-Premises
Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
High availability
DB s/w installs
OS installation
you
Scaling
App optimization

4. If You Host Your Databases in EC2
Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
Scaling
High availability
DB s/w installs
OS installation
you
App optimization

5. If You Choose a Managed Database Service
Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
App optimization
High availability
DB s/w installs
OS installation
you
Scaling
Database Tuning
Design Consultation
App optimization
Best Practices

6. Relational databases
Fully managed and secure
Fast, predictable performance
Simple and fast to scale
Low cost, pay for what you use
Amazon
RDS
Amazon Aurora

7. MySQL-compatible relational database
Performance and availability of
commercial databases
Simplicity and cost-effectiveness of
open-source databases
What is Amazon Aurora?

8. Database architectures in last 30 years
Even when you scale it out, you’re still replicating the same stack
SQL
Transactions
Caching
Logging
SQL
Transactions
Caching
Logging
Application
SQL
Transactions
Caching
Logging
SQL
Transactions
Caching
Logging
Application
SQL
Transactions
Caching
Logging
SQL
Transactions
Caching
Logging
Storage
Application

9. A service-oriented architecture applied to the database
Moved the logging and storage layer into a
multi-tenant, scale-out database-optimized
storage service
Integrated with other AWS services like
Amazon EC2, Amazon VPC, Amazon
DynamoDB, Amazon SWF, and Amazon
Route 53 for control plane operations
Integrated with Amazon S3 for continuous
backup with 99.999999999% durability
Control planeData plane
Amazon
DynamoDB
Amazon SWF
Amazon Route 53
Logging + Storage
SQL
Transactions
Caching
Amazon S3
1
2
3

10. Fastest growing
service in AWS
history
Business applications
Web and mobile
Content management
E-commerce, retail
Internet of Things
Search, advertising
BI, analytics
Games, media
Aurora customer adoption

11. Expedia: On-line travel marketplace
 Real-time business intelligence and analytics on a
growing corpus of on-line travel marketplace data.
 Current Microsoft SQL Server–based architecture
is too expensive. Performance degrades as data
volume grows.
 Cassandra with Solr index requires large memory
footprint and hundreds of nodes, adding cost.
Aurora benefits:
 Aurora meets scale and performance
requirements with much lower cost.
 25,000 inserts/sec with peak up to 70,000. 30 ms
average response time for write and 17 ms for
read, with 1 month of data.
World’s leading online travel
company, with a portfolio that
includes 150+ travel sites in 70
countries.

12. New Regions

13. 13 Regions
35 Availability Zones
63 Edge Locations
AWS Global Infrastructure

14. July 2015
• Virginia
• Oregon
• Ireland
Amazon Aurora Regions

15. October 2015
• Tokyo
Amazon Aurora Regions

16. February 2016
• Sydney
Amazon Aurora Regions

17. March 2016
• Seoul
Amazon Aurora Regions

18. June 2016
• Mumbai
Amazon Aurora Regions

19. Cross Region Read Replicas

20. Cross Region Read Replicas
• Launched 6/1/2016
• Features
• Additional 15 Read
Replicas in New Region
• Very Low RPO & RTO
• Unencrypted Clusters
• Use Cases
• Cross Region Disaster
Recovery
• Cross Region Migration
• Regional Availability

21. Cross Region Read Replicas

22. Cross Region Read Replicas

23. Cross Region Read Replicas

24. Cross Region Read Replicas

25. Cross Region Read Replicas

26. Cross Region Read Replicas

27. Local Time Zone Support

28. Local Time Zone support for Amazon Aurora
• Launched 3/1/2016
• Features
• Default Time Zone is UTC
• Set as Cluster Parameter
• Time Zone Applied for New Connections
• Cross Region Uses Different Parameter Groups
• Restore from Cluster Snapshot – Defaults to UTC
• Use Cases
• Application Compatibility
• Reporting

29. Local Time Zone support for Amazon Aurora

30. Local Time Zone support for Amazon Aurora

31. Local Time Zone support for Amazon Aurora

32. Cross Account Snapshot
Sharing

33. Cross Account Snapshot Sharing
• Launched 5/18/2016
• Features
• Share with Specific Accounts
• Create Public Snapshots
• Manually Generated, Unencrypted Snapshots
• Use Cases
• Separation of Environments (dev, test, prod)
• Partnering (vendors, customers)
• Data Dissemination (research, public datasets)

34. Cross Account Snapshot Sharing

35. Cross Account Snapshot Sharing

36. Cross Account Snapshot Sharing

37. Enhanced Monitoring

38. Enhanced Monitoring
• Launched 12/18/2015
• Features
• 53 Metrics (CPU, Memory, Disk, Swap, Processes, File
System)
• Configure Granularity (1-60 seconds)
• Use Cases
• Diagnose Bottlenecks via Console
• Metrics Extraction Filter
• CloudWatch Alerts (Add Read Replica)

39. Enhanced Monitoring
Amazon CloudWatch
metrics 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

40. Enhanced Monitoring

41. Enhanced Monitoring

42. Enhanced Monitoring

43. Additional Failover Control

44. Additional Failover Control for Amazon Aurora
• Launched 3/14/2016
• Features
• Up to 15 Read Replicas
• Specify Failover Order
• Specify High Failover Order for Application Instances
• Use Cases
• Isolate Application Instances from Failover
• More Control Over Failover Precedence

45. Additional Failover Control for Amazon Aurora

46. Encryption at Rest

47. Encryption at Rest
• Launched 12/7/2015
• Features
• AWS Managed or Customer Managed Key (KMS)
• AES-256 (In-Transit & at Rest)
• Database, Logs, Backups, Snapshots, Read Replicas
• Specify at Creation
• Annual Key Rotation
• CloudTrail Audit
• Can Create from Unencrypted Backup
• Use Cases
• Protect Data at Rest
• Compliance (PCI, SOC 1/2/3, ISO 27001/9001, ISO 27017/27018)

48. Encryption at Rest

49. Binary Snapshot Ingestion
from S3

50. Binary Snapshot ingestion from S3
• Launched 7/20/2016
• Features
• Replaces mysqldump
• Percona XtraBackup
• Simplifies Import of Complex Databases
• No Performance Impact on Source Database
• Migrate MySQL on EC2 or on-premises

51. Binary Snapshot ingestion from S3
• Manual Options
• User Accounts
• Functions
• Stored Procedures
• Time Zone Information
• Does Not Support Partial Backups
• --include
• --tables-file
• --databases

52. Binary Snapshot ingestion from S3
• Best Practices
• Large Files – Use Multi-Part Upload / Split Option
• Long Distances – Use S3 Transfer Acceleration
• Backup Format Must Match File Extension
• Gzip
• tar
• Percona xbstream
• Use Cases
• InnoDB or MyISAM table spaces

53. Binary Snapshot ingestion from S3

54. Reader Endpoint for Amazon
Aurora

55. Reader Endpoint for Amazon Aurora
• Launched 9/8/2016
• Features
• Single Reader Endpoint
• May Replace MariaDB
Connector Load Balancing
• During Failover, read-only
connections dropped
• Use Cases
• Load Balancing
• High Availability

56. Reader Endpoint for Amazon Aurora
• Load Balancing
• Point all Readers to Reader Endpoint
• New Read Replicas are put into rotation
• Retired Read Replicas are taken out of rotation
• Load Balances Connections Not Queries
• Check DNS Cache Settings if Connections are Lopsided

57. Reader Endpoint for Amazon Aurora
• Failover
• Point all Writers to Cluster Endpoint
• Ensure Read Replicas are in Different Availability Zones
• DNS Change Points to Read Replica in Priority Order
• Read Only Connections to Replica are Dropped
• May see temporary traffic to new master while DNS changes
• Make sure to use Failover Priorities

58. Demo

59. Thank you!
Steve Abraham – abrsteve@amazon.com