最後更新: 2020-10-17

S3

(The default download protocol is HTTP. A BitTorrent? protocol interface is provided to lower costs for high-scale distribution.)
(Uses standards-based REST and SOAP interfaces designed to work with any Internet-development toolkit.)
Authentication mechanisms are provided to ensure that data is kept secure from unauthorized access. Objects can be made private or public, and rights can be granted to specific users.
(A bucket can be stored in one of several Regions. You can choose a Region to optimize for latency, minimize costs, or address regulatory requirements.)

Unused capacity under the free usage tier does not roll over from month to month

最後更新: 2020-10-16

介紹

Aurora 是一個 SaaS - RDS (Relational Database Service)

特點

• high performance (5x MySQL)
• up to 15 low-latency read replicas (Asynchronous, In-region, milliseconds)
• cross-region replicas (Physical / Logical replication)
• point-in-time recovery(up to 5 minutes in the past), DB Snapshot
• continuous backup to S3
• Amazon Aurora automatically maintains 6 copies of your data across 3 AZs
• encryption through AWS Key Management Service (KMS)
• encryption of data in transit using SSL
• compatible with existing MySQL and PostgreSQL
• prioritize certain replicas as failover targets over others
• Aurora Multi-Master
• Aurora Parallel Query

===========

High Availability and Replication

Each 10GB chunk of your database volume is replicated six ways

 - loss of up to two copies of data without affecting database write availability and

 - up to three copies without affecting read availability

Aurora Replicas in the same AWS Region share the same underlying storage as the primary instance

Amazon RDS will automatically detect a problem with your primary instance and trigger a failover.

If you are using the Cluster Endpoint,

  your read/write connections will be automatically redirected to an Amazon Aurora Replica that will be promoted to primary.

===========

Aurora Parallel Query

No changes in query syntax are required.

(The query optimizer will automatically decide whether to use PQ for your specific query)

may incur higher IO costs

(PQ requires all data to be scanned at the storage layer)

PQ can be enabled and disabled dynamically at both the global and session level