Streamline Your Data Operations : Setting Up Amazon Aurora with Reader/Writer Endpoints.

Reasons to Use Amazon Aurora with Reader/Writer Endpoints

High Availability : Amazon Aurora automatically replicates your data across multiple availability zones, ensuring your databases are always accessible and reducing downtime.

Scalability : With Reader/Writer endpoints, you can easily scale your database workloads. The writer endpoint handles all write operations, while reader endpoints distribute read traffic, allowing you to scale read capacity as needed.

Improved Performance : Aurora is designed for high throughput and low latency. By separating read and write operations, you can optimize performance for both types of requests, enhancing overall application responsiveness.

Cost Efficiency : With the ability to scale read replicas, you can optimize resource usage and reduce costs. Pay only for the resources you need, especially during peak traffic times.

Simplified Management : Using Amazon RDS for Aurora simplifies database management tasks such as backups, patching, and monitoring, allowing you to focus on your applications rather than infrastructure.

MySQL Compatibility : If you’re already using MySQL, migrating to Aurora is straightforward due to its compatibility. This minimizes the learning curve and allows for quick adoption.

Data Security : Amazon Aurora provides built-in security features, including encryption at rest and in transit, as well as network isolation options to protect your data.

The primary reason to create separate Aurora DB reader and writer instances is to enable efficient scaling for read-heavy workloads by allowing you to independently add more read replicas (readers) to handle high volumes of read requests without impacting the performance of the primary write instance (writer).

Step 1 : Select Standard create then choose the Engine type we are going with Aurora(MySql Compatible)Amazon aurora compatibility with mysql with different versions.

Step 2 : Select Dev/Test as a Template. Give a database identifier then fill the credentials with self managed.

Step 3 : Select Aurora I/O-Optimized( It offers improved performance, increasing throughput and reducing latency to support your most demanding workloads ). Select burstable includes t classes (benefits of t classes can handle sudden spikes in workload without compromising overall performance )

Step 4 : On connectivity select the default vpc as given then choose public access Yes. Then choose the security group create a new one.

Step 5 : Leave everything as default and hit the create database to create one.

Step 6 : Edit the insbound rules of the created database security group.

Step 7 : Here we can see our database is successfully created withreader and writer instance.

Step 8 : Here we are gonna see a trick if we copy the endpoint URL of Writer instance then we can do create or erase database from the terminal. On the other hand if we copy the endpoint URL of Reader instance we can’t create from it.

Step 9 : Copy the writer endpoint and try something new to create. Then we create one database from writer instance.

Step 10 : Copy the reader instance endpoint URL then connect with it.

Step 11 : Sorry we can not create and databse for us the reason is that dispalys on the terminal “Running-read-only-mode“

Step 12 : After all that practice demo stauff allow me to waive off my database which we’ve createted for our practice purpose.

thank Yu !!