Amazon Cloud Concepts Learning --> Day19
Types of Aurora Endpoints
A host address and port are included in an Aurora-specific URL that represents an endpoint. An Aurora DB cluster may provide the following kinds of endpoints.
- Cluster Endpoint
An Aurora DB cluster's cluster endpoint, also known as a writer endpoint, establishes a connection with the cluster's primary database instance. Only this endpoint is capable to perform write operations such DDL statements.
One primary DB instance and one cluster endpoint are present in every Aurora DB cluster.
- Reader Endpoint
For read-only connections to an Aurora DB cluster, a reader endpoint offers load balancing functionality.
It is only used for read operations such as Select queries.
Each Aurora DB cluster has one reader endpoint.
- Custom Endpoint
Represents a set of DB instances that you choose.
When you connect to the endpoint, Aurora performs load balancing and chooses one of the instances in the group to handle the connection.
You define which instances this endpoint refers to, and you decide what purpose the endpoint serves.
Up to 5 custom endpoints can be created and by default Aurora DB Cluster has no custom endpoint.
- Instance Endpoint
Connects to a specific DB instance within an Aurora Cluster.
In a DB cluster, every DB instance has a distinct instance endpoint.
DB cluster has a single instance endpoint for its primary database instance.
Single instance endpoint for each of its Aurora Replicas.
Aurora Replicas
There are two types of Replications.
| Feature | Aurora Replica | MySQL Replica |
| Number of Replica | Up to 15 | Up to 5 |
| Replication Type | Asynchronous(milliseconds) | Synchronous(seconds) |
| Replication Location | In-region | Cross-Region |
| Automated failover | Yes | No |
| Performance impact on primary | Low | High |
Aurora Backtrack & Limitations
Backtracking "rewinds" the DB cluster to the time you specify.
Limitations
Database clusters that were established with the Backtrack functionality enabled are the only ones that can do backtracking.
A backtrack window has a 72-hour restriction.
Backtracking causes a brief DB instance disruption.
Aurora Serverless
An on-demand, auto-scaling configuration of Amazon Aurora is called Amazon Aurora Serverless.
Accessible for PostgreSQL and MySQL compatible versions.
The database adjusts its capacity and begins, stops, and shuts down automatically based on application needs.
It is an easy-to-use, reasonably priced solution for irregular, sporadic, or unexpected workloads.
When the database is operational, you pay for the capacity that you utilize on a per-second basis.
Aurora Storage & Reliability
Aurora reduces the likelihood of data loss due to disk failure by maintaining multiple copies of your data in three different Availability Zones.
Failures in the disk volumes that comprise the cluster volume are automatically detected by Aurora. When a disk volume section malfunctions, Aurora fixes it right away.
Aurora is built to function without the binary log, recovering from an unexpected restart with near-instantaneous performance. After an unexpected restart, Aurora recovers asynchronously on parallel threads, allowing your database to be accessible right away.
Aurora Security
Use IAM to control access.
Using a VPC security group, you may restrict which devices and Amazon EC2 instances can establish connections to the endpoint and port of the DB instance for Aurora DB clusters in a VPC.
Does not allow for SSH access to the servers that are the foundation.
Allows for KMS-based encryption when at rest.
Additional Resources
https://aws.amazon.com/rds/aurora/faqs/
"Thank you for reading! If you found this blog helpful, don't forget to subscribe and follow for more insightful content. Your support keeps me motivated to bring you valuable insights. Stay updated and never miss out on our latest posts. Feel free to leave comments or suggestions for future topics. Happy learning!"
https://awslearner.hashnode.dev/amazon-web-services-via-category