Amazon Relational Database Service – How is it different to what you do today ?

© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Amazon Relational Database Service –
How is it Different From What you do Today?
Blair Layton
Business Development Manager
Database Services

What to Expect from the Session
• Amazon RDS overview
• Security
• Sizing – (CPU, RAM, Storage and Networking)
• Scaling
• Backup and Recovery
• High Availability and Disaster Recovery
• Monitoring and Metrics
• Migrating to RDS
• Licensing / Marketplace
• Cost Management
• Q&A!

© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Why Managed Databases?
How much time do your DBAs and other IT staff spend on:
• Provisioning hardware and storage
• Installing, upgrading and patching software
• Documentation, licensing and training
• Backup & recovery, data load & unload
• Security

If you host your databases on-premises
Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
Scaling
High availability
DB s/w installs
OS installation
App optimization

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
App optimization

If you choose a managed DB service like RDS
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
Scaling

differentiated effort increases the
uniqueness of an application

Relational Databases
Managed Service
Simple and fast to scale
Fast, predictable performance
Low cost, pay for what you use
Amazon
RDS
Amazon
Aurora

Selected Amazon RDS customers

Selected Amazon Aurora customers

MySQL to Aurora MySQL
35 million members on it’s site
Many interdependent applications built over the
last 15 years with unique High IOPS
requirements
Migration from legacy cloud service to AWS
Combination of migration to MySQL on EC2 and
Amazon Aurora
Benefits:
• DMS reduced the time required to migrate our
databases by 40 percent
• Realized 55 percent cost savings by moving some
databases to Amazon Aurora

Security

Secure Network Configuration
Amazon Virtual Private Cloud (VPC)
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

Database IP Firewall Protection
Security Groups
Protocol Port Range Source
TCP 3306 172.31.0.0/16
TCP 3306 “Application
security group”
Corporate address admins
Application tier

Governed Access to RDS by User and Role
You can use AWS Identity and Access Management (IAM)
to control who can perform actions on RDS
Users and DBAApplications DBA and Ops
Your database RDS
Controlled with IAMControlled with database grants

In Transit Encryption - SSL
Available for all six engines
Database traffic encryption

At-Rest Encryption
• DB instance storage
• Automated backups
• Read Replicas
• Snapshots
• Available for all six engines
• No additional cost
• Support compliance requirements

Compliance
Singapore MTCS
27001/9001
27017/27018

Feature Aurora (MySQL) MySQL MariaDB PostgreSQL Oracle SQL Server
SOC 1, 2 and 3      
ISO 27001/9001      
ISO 27017/27018      
PCI DSS      
FedRAMP Ready  Ready 
HIPAA BAA    
Singapore MTCS    
RDS Engine Compliance Matrix

Sizing on RDS

Servers are Now Instances
RDS instances consist of the following characteristics:
• vCPUs: Hyper-threads on Intel CPUs with 1 – 40 vCPUs
• RAM: 1 GiB – 244 GiB
• Network Throughput: Up to 10,000 Mbps
• EBS Dedicate Network Throughput: Up to 4,000 Mbps
• Allocated EBS Storage: Up to 16 TB
• Aurora uses a separate storage service with up to 64 TB

Storage: What is EBS?
• Network block storage as a service
• EBS volumes attach to any Amazon EC2 instance in the
same Availability Zone
• Designed for five nines of availability
• 5 types of storage

EBS Volume Types for RDS
Magnetic General purpose (SSD) Provisioned IOPS
(SSD)

General Purpose (SSD) – Burst & baseline
16 KiB I/O size

Provisioned IOPS (SSD)
• 50:1 ratio. E.g., a 100 GiB max IOPS is 5,000 and any volume >=400 GiB
allows up to the 20,000 IOPS maximum.
• The throughput limit of io1 volumes is 256 KiB for each IOPS provisioned, up
to a maximum of 320 MiB/s (at 1,280 IOPS).

EBS Volume Types - Summary
General Purpose (SSD) Provisioned IOPS (SSD) Magnetic
Recommend use cases
Boot volumes
Small to med DBs
Dev and test
I/O-intensive workloads
Large DBs
Cold storage
Storage media SSD-backed SSD-backed Magnetic-backed
Volume size 1 GB - 16 TB 4 GB - 16 TB 1 GB - 1 TB
Max IOPS per volume 10,000 IOPS 20,000 IOPS 40-200 IOPS
Burst < 1 TB to 3000 IOPS baseline baseline
Read and write peak throughput 160 MB/s 320 MB/s ~40-90 MBps
Max IOPS per instance (16k) 75,000 75,000 48,000
Peak throughput per instance 1,750MB/s 1,750MB/s 800 MB/s
Latency (random read) 1-2 ms 1-2 ms 20-40 ms
API Name gp2 io1 standard
Price* $.10/GB-month
$.125/GB-month
$.065/provisioned IOPS
$.05/GB-month
$.05/ 1M I/O

Choose Your Instance Wisely
Balance the vCPUs, RAM, network and storage
Use your existing database metrics to guide sizing on AWS

Scaling on RDS

Scaling up—or down
• Handle higher load or lower usage
• Control costs

Scaling up—or down
AWS Management Console

Scaling Reads with 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
Intra-region and cross-region
with:
• MySQL
• MariaDB
• PostgreSQL
• Aurora

Read Replicas for Amazon Aurora
AZ 1
AZ 3AZ 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

Read Replicas— Oracle Database and SQL Server
Options
• Oracle GoldenGate
• AWS Database Migration Service
• Third-party replication products
• Snapshots

Backup and Recovery

Automatic Backups
MySQL, PostgreSQL, MariaDB, Oracle, SQL Server
• Scheduled daily backup of entire instance using incremental snapshots
• Archive database change logs every 5 minutes
• 35 day retention for backups
• Multiple copies in each AZ where you have instances for a deployment
Aurora
• Automatic, continuous, incremental backups
• Point-in-time restore
• No impact on database performance
• 35 day retention

Restoring
• Restoring creates an entire new database instance with a
new endpoint
• Instance configuration is just like creating a new instance

User 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

Snapshots
Use cases
• Resolve production issues
• Nonproduction environments
• Point-in-time restore
• Final copy before terminating a database
• Disaster recovery
• Cross-region copy
• Copy between accounts

High Availability
and
Disaster Recovery

Minimal deployment—single AZ
Availability Zone
AWS Region
10.1.0.0/16
10.1.1.0/24
Amazon EBS volume

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

High availability—Multi-AZ to DNS
dbinstancename.1234567890.us-west-2.rds.amazonaws.com:3006

High availability—Amazon Aurora storage
• Storage volume automatically grows up to 64 TB
• 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

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 3AZ 2
Primary
Node
Primary
Node
Primary
Node
Primary
Node
Primary
Node
Secondary
Node
Primary
Node
Primary
Node
Secondary
Node

Metrics and Monitoring

Standard monitoring
Amazon CloudWatch
metrics for Amazon RDS
 CPU utilization
 Storage
 Memory
 Swap usage
 DB connections
 I/O (read and write)
 Latency (read and write)
 Throughput (read and write)
 Replica lag
 Many more
Amazon CloudWatch Alarms
 Similar to on-premises custom
monitoring tools

Enhanced Monitoring
Access to over 50 new CPU, memory, file system, and disk I/O metrics as
low as 1 second intervals

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)

Native and 3rd-Party Tools
Native Tools: E.g. Oracle Enterprise Manager and SQL
Server Management Studio
Third-party Tools: E.g. New Relic, Toad, Datadog,
Webyog, Navicat
Integration Tools: E.g. Talend, Informatica, Attunity

Well established ecosystem
Business Intelligence Data Integration Query and Monitoring SI and Consulting
Source: Amazon
“We ran our compatibility test suites against Amazon Aurora and everything
just worked." - Dan Jewett, Vice President of Product Management at Tableau

Migrating to RDS

AWS Database Migration Service (AWS DMS)
DMS migrates databases to AWS easily and
securely with minimal downtime. It can migrate
your data to and from most widely used
commercial and open-source databases.
Amazon Aurora

New NoSQL support
Migrate to AWS
• Move from MongoDB to Amazon DynamoDB
• Move from MongoDB to relational db’s
Move between NoSQL and SQL
• Change technologies
Amazon Aurora
DynamoDB
DynamoDB
RDS

AWS Schema Conversion Tool (AWS SCT)
SCT helps automate many database schema and
code conversion tasks when migrating between
database engines or data warehouse engines
Amazon Aurora

Licensing on RDS

Disclaimer
• This session must not to be used as guidance for
licensing purchases or compliance, it is merely
informational and non-binding. All licensing decisions
must be agreed with Microsoft and Oracle.
• You must review your Microsoft PUR and Oracle license
agreement to understand your specific usage rights.
Your Microsoft PUR and Oracle license agreement may
be customized and therefore different than the
information in this presentation.

Licensing Terms
• BYOL – Bring your own license based on license portability rules of
your vendor
• LI – License included, AWS provides the license as part of the
hourly instance fee
• Dedicated Instances – AWS instances where the underlying
physical hardware is not shared
• Dedicated Hosts – A dedicated AWS physical server
• Virtual Cores – Directly mapped to physical CPU cores
• vCPUs – Hyper-threaded virtual cores

SQL Server License Mobility on AWS
You are responsible for obtaining the licenses required for eligible Microsoft
applications running in the AWS cloud using the License Mobility through Software
Assurance benefit, and for complying with all applicable Microsoft licensing
requirements. Under the PUR, the number of licenses required varies based on the
instance type, version of SQL Server, and the Microsoft licensing model you
choose.
For “Licensing by Individual Virtual OSE” of Microsoft SQL Server 2014 (and
permitted instances of Microsoft SQL Server 2012), the July 2014 version of the
PUR states, “The number of licenses required equals the number of Virtual Cores in
each Virtual OSE in which you will run the server software, subject to a minimum of
four licenses per Virtual OSE.” The July 2014 version of the PUR defines a “Virtual
Core” as “the unit of processing power in a virtual hardware system. A Virtual Core
is the virtual representation of one or more hardware threads.”
http://aws.amazon.com/windows/resources/licensemobility/sql/

Engine Versions License Included BYOL
SQL Server 2008 R2
2012, 2014,
2016
Express Edition
Web Edition
Standard Edition
Enterprise Edition
Standard Edition*
Enterprise Edition*
* Requires Software
Assurance/License Mobility
RDS SQL Server - Versions and Licensing
For fleet migrations to AWS it is recommended to use EC2 Dedicated Hosts to
obtain licensing costs similar to on-premise. For example:
• RDS db.r3.8xlarge with 32 vCPUs = 32 licenses on RDS
• EC2 r3 dedicated host = 20 licenses

Oracle License Portability to AWS
All Oracle Software licenses are fully portable to Amazon Web Services
• Enterprise License Agreement (ELA)
• Unlimited License Agreement (ULA)*
• Business Process Outsourcing (BPO)
• Oracle Partner Network (OPN)
Processor & Socket Licensing:
• Standard Edition Licenses
• 1 socket license for every 4 vCPUs (round up, e.g. 6 vCPUs = 2 sockets)
• Enterprise Edition Licenses
• 1 license for 2 vCPUs for instances with hyper-threading
• 1 license per vCPU for instances without hyper-threading
• Standard named user plus licensing applies, including counting
the minimums where applicable
Oracle Cloud Licensing Policy
http://www.oracle.com/us/corporate/pricing/cloud-licensing-070579.pdf

RDS Oracle - Versions and Licensing
Engine Versions License Included BYOL
Oracle Database 11gR2 (11.2.0.4)
12c (12.1.0.2)
Standard Edition One
Standard Edition Two
Standard Edition One
Standard Edition Two
Standard Edition
Enterprise Edition
• Oracle changed its licensing policy in January, 2017
• Please Check with 3rd-party licensing specialists such as Palisade Compliance to
confirm your Oracle licensing requirements on AWS.
• RDS Oracle Standard Edition One follows the original licensing metrics.

Cost Management
on RDS

Cost Management
Use Stop/Start: Stop dev/test instances when you don’t need them.
E.g. Stop at 8 pm and start at 8 am.
Right size and scale up/down: It’s easy to change instance sizes and
types, so don’t over provision like you do on-prem.
Choose the right storage: PIOPS is great for performance, but costs
a lot more than general purpose SSD.
Choose the right edition: No, you don’t need Oracle Database EE for
everything!
Buy RIs: Databases are on ALL the time, buy RIs!

Feature Aurora MySQL MariaDB PostgreSQL Oracle SQL Server
VPC      
High availability      
Instance Scaling      
Encryption      
Read replicas     Oracle
Golden Gate
/ DMS
DMSCross region
replicas
   
Max Storage 64 TB 6 TB 6 TB 6 TB 6 TB 16 TB
Scale Storage Auto scaling    
Provisioned
IOPS
NA 30,000 30,000 30,000 30,000 20,000
Largest Instance R3.8XL R3.8XL
M4.10XL
R3.8XL
M4.10XL
R3.8XL
M4.10XL
R3.8XL
M4.10XL
R3.8XL
M4.10XL
RDS Engine Capability Matrix

Thank You for Attending the Webinar
We hope you found it interesting! A kind reminder to complete the survey.
Let us know what you thought of today’s event and how we can improve
the event experience for you in the future.
aws-apac-marketing@amazon.com
twitter.com/AWSCloud
facbook.com/AmazonWebServices
youtube.com/user/AmazonWebServices
slideshare.net/AmazonWebServices
twitch.tv/aws

New to AWS
Introductory labs
and videos can
help you ramp up
Start learning
Take a Class
Build technical
skills and learn
best practices from
an accredited
instructor
Find a class
AWS Certification
Validate knowledge
and show expertise
with industry
recognized
certifications
Get Certified
Online Labs
Take an online
Self-Paced Lab to
get hands-on-
practice with AWS
services
Start practicing
Learn more: aws.amazon.com/training

Amazon Relational Database Service – How is it different to what you do today ?

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Amazon Relational Database Service – How is it different to what you do today ?

Similar to Amazon Relational Database Service – How is it different to what you do today ? (20)

More from Amazon Web Services

More from Amazon Web Services (20)

Amazon Relational Database Service – How is it different to what you do today ?