Why Use Amazon Aurora?
- Aurora is MySQL and PostgreSQL compatible. This implies that an Aurora cluster may be created as a MySQL (5.6 OR 5.7) database instance or a PostgreSQL database instance. Open source MySQL and PostgreSQL databases may be migrated to Aurora.
- With its performance and high availability, Aurora brings the advantages of commercial databases to open source databases.
- Aurora MySQL is 5x faster than a non-Aurora MySQL database instance. Aurora PostgreSQL is 3x faster than a non-Aurora PostgreSQL database.
- Aurora is a RDS managed database, which implies that most of the administration tasks including provisioning, setup, patching, and backups on S3 are automated.
- Aurora provides replication across three availability zones. Failure of a single Availability zone does not cause the database to become unavailable. Up to 15 read replicas may be added across the three zones.
- Aurora is fault-tolerant. Aurora replicates 6 copies of a database across three availability zones. Instance failover takes less than 1/2 minute.
- Aurora auto scales up to 64 TB per instance.
- Aurora is integrated with the other AWS services including CloudWatch, VPC, and IAM.
In this article, we shall create an Amazon Aurora cluster. This article has the following sections:
- Setting the Environment
- Creating an Aurora Cluster
- Configuring Accessibility to the Aurora Cluster
Figure 19: Security group link
Select the Inbound tab and click Edit to modify the inbound rule, as shown in Figure 20.
Figure 20: Security group>Inbound>Edit
In Edit inbound rules, modify Source to Anywhere and click Save (see Figure 21).
Figure 21: Modifying Inbound rules
The Inbound rules get modified, as shown in Figure 22.
Figure 22: Modified Inbound rules
In this article, we introduced Amazon Aurora and the benefits it offers. We started by creating an Aurora cluster compatible with MySQL database and configuring accessibility to the cluster.