Deep Dive on Amazon Relational Database Service (November 2016)
2 likes380 views
The document provides an extensive overview of Amazon Relational Database Service (Amazon RDS), covering aspects such as security, metrics, monitoring, high availability, scaling, backups, snapshots, and migration options. It elaborates on RDS features like fully managed storage, encryption options, and compliance standards for various database engines. Additionally, it discusses the mechanisms for managing databases efficiently, including resource scaling and data migration services.
![Simulating Amazon Aurora failures
ALTER SYSTEM CRASH [ INSTANCE | DISPATCHER | NODE ];
ALTER SYSTEM SIMULATE percentage_of_failure PERCENT
• READ REPLICA FAILURE [ TO ALL | TO "replica name" ]
• DISK FAILURE [ IN DISK index | NODE index ]
• DISK CONGESTION BETWEEN minimum AND maximum
MILLISECONDS [ IN DISK index | NODE index ]
FOR INTERVAL quantity [ YEAR | QUARTER | MONTH | WEEK| DAY |
HOUR | MINUTE | SECOND ];
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Aurora.Managing.html](https://image.slidesharecdn.com/deepdiveonamazonrelationaldatabaseservice-161122114947/85/Deep-Dive-on-Amazon-Relational-Database-Service-November-2016-33-320.jpg)
![Scaling on demand – Cloudwatch & AWS Lambda
import boto3
import json
client=boto3.client('rds')
def lambda_handler(event, context):
message = event['Records'][0]['Sns']['Message']
parsed_message=json.loads(message)
db_instance=parsed_message['Trigger']['Dimensions'][0]['value']
print 'DB Instance: ' + db_instance
response=client.modify_db_instance(DBInstanceIdentifier=db_instance,
DBInstanceClass='db.m4.large',
ApplyImmediately=True)
print response
SNS LambdaCloudwatchRDS](https://image.slidesharecdn.com/deepdiveonamazonrelationaldatabaseservice-161122114947/85/Deep-Dive-on-Amazon-Relational-Database-Service-November-2016-44-320.jpg)
Deep Dive on Amazon Relational Database Service (November 2016)
- 1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Deep Dive on Amazon RDS Julien Simon, Principal Technical Evangelist, AWS julsimon@amazon.fr @julsimon
- 2. What to expect • Amazon RDS overview (super quick) • Security • Metrics and monitoring • High availability • Scaling on RDS • Backups and snapshots • Migrating to RDS • Q&A
- 3. No infrastructure management Scale up/down Cost-effective Instant provisioning Application compatibility Amazon Relational Database Service (Amazon RDS) https://aws.amazon.com/rds/whats-new/
- 4. Amazon RDS engines Commercial Open source Amazon Aurora
- 5. Selected Amazon RDS customers
- 6. Selected Amazon Aurora customers
- 7. Trade-offs with a managed service Fully managed host and OS • No access to the database host operating system • Limited ability to modify configuration that is managed on the host operating system • No functions that rely on configuration from the host OS Fully managed storage • Max storage limits • Microsoft SQL Server—4 TB • MySQL, MariaDB, PostgreSQL, Oracle—6 TB • Aurora—64 TB • Growing your database is a process
- 8. http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.PostgreSQL.CommonDBATasks.html http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.MySQL.CommonDBATasks.html Amazon RDS: the fine print J http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.MariaDB.Parameters.html
- 9. Security
- 10. Amazon Virtual Private Cloud (VPC) Securely control network configuration Availability Zone AWS Region 10.1.0.0/16 10.1.1.0/24 Manage connectivity AWS Direct Connect VPN connection VPC peering Internet gateway Routing rules
- 11. Security groups Database IP firewall protection Protocol Port Range Source TCP 3306 172.31.0.0/16 TCP 3306 “Application security group” Corporate address admins Application tier
- 12. Compliance Singapore MTCS 27001/9001 27017/27018 https://aws.amazon.com/compliance/
- 13. MySQL and Oracle • SOC 1, 2, and 3 • ISO 27001/9001 • ISO 27017/27018 • PCI DSS • FedRAMP • HIPAA BAA • UK government programs • Singapore MTCS Compliance SQL Server and PostgreSQL • SOC 1, 2, and 3 • ISO 27001/9001 • ISO 27017/27018 • PCI DSS • UK government programs • Singapore MTCS
- 14. In-flight data encryption" SSL available for all six engines http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html
- 15. At-rest data encryption • DB instance storage • Automated backups • Read Replicas • Snapshots • Available for all six engines • No additional cost • Support compliance requirements • TDE also available for Oracle / SQL Server http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.Encryption.html
- 16. Amazon RDS encryption hints • You can only encrypt on new database creation • Encryption cannot be removed • Master and Read Replica must be encrypted • Unencrypted snapshots cannot be restored to encrypted DB • Aurora will allow this • You can create encrypted copies of your unencrypted snapshots • Cannot restore MySQL to Aurora or Aurora to MySQL • Cannot copy snapshots or replicate DB across regions
- 17. AWS KMS—RDS standard encryption Two-tiered key hierarchy using envelope encryption: • Unique data key encrypts customer data • AWS KMS master keys encrypt data keys Benefits: • Limits risk of compromised data key • Better performance for encrypting large data • Easier to manage small number of master keys than millions of data keys • Centralized access and audit of key activity Data key 1 Amazon S3 object Amazon EBS volume Data key 2 Data key 3 Data key 4 Custom" application Customer master" key(s) Amazon RDS instance https://aws.amazon.com/kms/
- 18. Your RDS instance + Data key Encrypted data key Encrypted" data Master key(s) in " customer’s account AWS KMS 1. RDS instance requests encryption key to use to encrypt data, passes reference to master key in account 2. Client request authenticated based on permissions set on both the user and the key 3. A unique data encryption key is created and encrypted under the KMS master key 4. Plaintext and encrypted data key returned to the client 5. Plaintext data key used to encrypt data and then deleted when practical 6. Encrypted data key is stored; it’s sent back to KMS when needed for data decryption How keys are used to protect your data https://aws.amazon.com/kms/
- 19. Enabling encryption with the AWS CLI aws rds create-db-instance --region us-west-2 --db-instance-identifier sg-cli-test --allocated-storage 20 --storage-encrypted --db-instance-class db.m4.large --engine mysql --master-username myawsuser --master-user-password myawsuser aws rds create-db-instance --region us-west-2 --db-instance-identifier sg-cli-test1 --allocated-storage 20 --storage-encrypted --kms-key-id xxxxxxxxxxxxxxxxxx --db-instance-class db.m4.large --engine mysql --master-username myawsuser --master-user-password myawsuser http://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html
- 20. IAM governed access You can use AWS Identity and Access Management (IAM) to control who can perform actions on RDS Users and DBA Applications DBA and Ops Your database RDS Controlled with IAM Controlled with database GRANTs
- 22. Standard monitoring Amazon CloudWatch metrics for Amazon RDS l CPU utilization l Storage l Memory l Swap usage l DB connections l I/O (read and write) l Latency (read and write) l Throughput (read and write) l Replica lag l Many more Amazon CloudWatch Alarms l Similar to on-premises custom monitoring tools *** NEW (Nov’11) price drop, longer retention & percentile monitoring https://aws.amazon.com/about-aws/whats-new/2016/11/announcing-cloudwatch-metrics-price- reduction-and-new-volume-based-pricing-tiers/ https://aws.amazon.com/blogs/aws/amazon-cloudwatch-update-percentile-statistics-and-new- dashboard-widgets/ https://aws.amazon.com/about-aws/whats-new/2016/11/cloudwatch-extends-metrics-retention-and- new-user-interface/
- 23. Enhanced Monitoring Access to over 50 new CPU, memory, file system, and disk I/O metrics " as low as 1 second intervals (sent to CloudWatch Logs) http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Monitoring.OS.html
- 24. Event notifications • Uses Amazon Simple Notification Service (Amazon SNS) to notify users when an event occurs • 17 different event categories (availability, backup, configuration change, and so on)
- 26. Minimal deployment—single AZ Availability Zone AWS Region 10.1.0.0/16 10.1.1.0/24 Amazon Elastic Block Store volume
- 27. High availability—Multi-AZ 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 Same instance type as master
- 28. High availability—Multi-AZ to DNS dbinstancename.1234567890.us-west-2.rds.amazonaws.com:3006
- 29. High availability—Amazon Aurora storage • Storage volume automatically grows up to 64 TB • 6 copies across 3 AZs • Quorum system for read/write; " latency tolerant • Peer-to-peer gossip replication to fill in holes • Continuous backup to Amazon S3 " (built for 11 9s durability) • Continuous monitoring of nodes " and disks for repair • 10 GB segments as unit of repair " or hotspot rebalance • Quorum membership changes do not " stall writes AZ 1 AZ 2 AZ 3 Amazon S3
- 30. High availability—Aurora nodes • Aurora cluster contains primary node and up to 15 secondary nodes • Failing database nodes are automatically detected and replaced • Failing database processes are automatically detected and recycled • Secondary nodes automatically promoted on persistent outage, no single point of failure • Customer application can scale out read traffic across secondary nodes AZ 1 AZ 3 AZ 2 Primary Node Primary Node Primary Node Primary Node Primary Node Secondary Node Primary Node Primary Node Secondary Node
- 31. Failover – MySQL vs Aurora App Running Failure Detection DNS Propagation Recovery Recovery DB Failure MySQL App Running Failure Detection DNS Propagation Recovery DB Failure Aurora with MariaDB driver 1 5 - 3 0 s e c 5 - 2 0 s e c 1 5 - 3 0 s e c Driver benefits https://mariadb.com/kb/en/mariadb/failover-and-high-availability-with-mariadb-connector-j/ https://mariadb.com/kb/en/mariadb/about-mariadb-connector-j/
- 32. Tips to improve recovery time with MySQL • DO NOT use the IP address to connect to RDS! • Set a low TTL on your own CNAME (beware if you use Java) • Avoid large number of tables : • No more than 1000 tables using Standard Storage • No more than 10,000 tables using Provisioned IOPS • Avoid very large tables in your database • Avoid large transactions • Make sure you have enough IOPS for recovery • Use RDS Events to be notified
- 33. Simulating Amazon Aurora failures ALTER SYSTEM CRASH [ INSTANCE | DISPATCHER | NODE ]; ALTER SYSTEM SIMULATE percentage_of_failure PERCENT • READ REPLICA FAILURE [ TO ALL | TO "replica name" ] • DISK FAILURE [ IN DISK index | NODE index ] • DISK CONGESTION BETWEEN minimum AND maximum MILLISECONDS [ IN DISK index | NODE index ] FOR INTERVAL quantity [ YEAR | QUARTER | MONTH | WEEK| DAY | HOUR | MINUTE | SECOND ]; http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Aurora.Managing.html
- 34. Scaling on RDS
- 35. Read Replicas Bring data close to your customer’s applications in different regions Relieve pressure on your master node for supporting reads and writes Promote a Read Replica to a master for faster recovery in the event of disaster"
- 36. Read Replicas Within a region • MySQL • MariaDB • PostgreSQL • Aurora Cross-region • MySQL • MariaDB • PostgreSQL • Aurora
- 37. Read Replicas for Amazon Aurora AZ 1 AZ 3 AZ 2 Primary Node Primary Node Primary node AZ 1 AZ 1 Primary Node Primary Node Read Replica node AZ 1 Primary Node Primary Node Read Replica node
- 38. Read Replicas—Oracle and SQL Server Options • Oracle GoldenGate • Third-party replication products • Snapshots
- 39. Scaling up—or down • Handle higher load or lower usage • Control costs
- 40. Scaling up—or down AWS Management Console
- 41. Scaling—single AZ With single AZ deployment, the master takes an outage dbinstancename.1234567890.us-west-2.rds.amazonaws.com:3006
- 42. Scaling—Multi-AZ With Multi-AZ, the standby gets upgraded first dbinstancename.1234567890.us-west-2.rds.amazonaws.com:3006
- 43. Scaling on a schedule – CLI or AWS Lambda import boto3 client=boto3.client('rds') def lambda_handler(event, context): response=client.modify_db_instance(DBInstanceIdentifier='sg-cli-test', DBInstanceClass='db.m4.xlarge', ApplyImmediately=True) print response #Scale down at 8:00 PM on Friday 0 20 * * 5 /home/ec2-user/scripts/ scale_down_rds.sh #Scale up at 4:00 AM on Monday 0 4 * * 1 /home/ec2-user/scripts/ scale_up_rds.sh aws rds modify-db-instance --db-instance-identifier sg-cli-test --db-instance-class db.m4.large --apply-immediately
- 44. Scaling on demand – Cloudwatch & AWS Lambda import boto3 import json client=boto3.client('rds') def lambda_handler(event, context): message = event['Records'][0]['Sns']['Message'] parsed_message=json.loads(message) db_instance=parsed_message['Trigger']['Dimensions'][0]['value'] print 'DB Instance: ' + db_instance response=client.modify_db_instance(DBInstanceIdentifier=db_instance, DBInstanceClass='db.m4.large', ApplyImmediately=True) print response SNS LambdaCloudwatchRDS
- 46. Backups MySQL, PostgreSQL, MariaDB, Oracle, SQL Server • Scheduled daily backup of entire instance • Archive database change logs • 35 day retention for backups • Multiple copies in each AZ where you have instances Aurora • Automatic, continuous, incremental backups • Point-in-time restore • No impact on database performance • 35 day retention
- 47. Restoring • Restoring creates an entirely new database instance • You define the instance configuration just like a new instance
- 48. Snapshots • Full copies of your Amazon RDS database that are different from your scheduled backups • Backed by Amazon S3 • Used to create a new RDS instance • Remain encrypted if using encryption
- 49. Snapshots Use cases • Resolve production issues • Build non-production environments • Point-in-time restore • Final copy before terminating a database • Disaster recovery • Cross-region copy • Copy between accounts
- 51. ü Move data to the same or different database engine ü Keep your apps running during the migration ü Start your first migration in 10 minutes or less ü Replicate within, to, or from Amazon EC2 or RDS AWS Database " Migration Service https://aws.amazon.com/dms/ http://docs.aws.amazon.com/dms/latest/userguide/CHAP_Introduction.Sources.html http://docs.aws.amazon.com/dms/latest/userguide/CHAP_Introduction.Targets.html https://aws.amazon.com/blogs/database/database-migration-what-do-you-need-to-know-before-you-start/
- 52. Customer premises Application Users AWS Internet VPN Start a replication instance Connect to source and target database Select tables, schemas, or databases Let the AWS Database Migration Service create tables, load data, and keep them in sync Switch applications over to the target at your convenience Keep your apps running during the migration
- 53. • Move your tables, views, stored procedures, and data manipulation language (DML) to RDS or Amazon Redshift • Highlight where manual edits are needed AWS Schema " Conversion Tool https://aws.amazon.com/dms/
- 54. Thank you!"