Search for a command to run...
Hi! I'm Guille Ojeda, Cloud Architecture Consultant To put it simply, I create simple solutions for complex technical problems.
My focus is on designing scalable, secure, and cost-effective cloud solutions that startups, scaleups and SMBs can lean on to grow.
I lean on years of experience in cloud architecture and consulting to deliver solutions that are easy to understand and manage.
No comments yet. Be the first to comment.
What Are Agentic AI Architectures? I won't waste your time with a long, fluffy introduction about how AI is changing the world. Let's get straight to the point: agentic AI architectures are fundamentally different from the prompt-response pattern you...
Building distributed systems requires putting a lot of attention on communication between components. These components often need to exchange information asynchronously, and that's where message queues and pub/sub systems are the go-to solution. AWS ...
Database failures are inevitable. Even with the most reliable hardware and software, something will eventually break. AWS RDS Multi-AZ deployments promise to handle these failures gracefully, automatically failing over to a standby database when prob...
There are two managed relational database services in AWS: Amazon Relational Database Service (RDS) and Amazon Aurora. Both provide the benefits of a fully managed database solution, but they have distinct features and use cases. In this article, we'...
Containers offer a lightweight, portable, and scalable solution for running software consistently across different environments. But as the number of containers grows, managing them becomes increasingly complex. That's where container orchestration c...
If you're managing your databases in the cloud with AWS RDS or Aurora instances, choosing the right instance size is crucial. You want to ensure that your instance can handle the traffic generated by your application while also avoiding overprovisioning and keeping costs down. In this guide, we will provide you with best practices for rightsizing your AWS RDS or Aurora instance.
Before diving into rightsizing, it's essential to know the basics of AWS RDS and (Aurora instances)[https://blog.guilleojeda.com/understanding-aws-aurora-instance-types?utm_source=blog&utm_medium=hashnode]. RDS is a fully managed service that makes it easy to set up, operate, and scale a relational database in the cloud. Aurora, on the other hand, is a MySQL and PostgreSQL-compatible relational database engine that is fully managed and designed to be more performant than RDS. Both RDS and Aurora instances come in different sizes, or "instance types," that are optimized for different workloads.
The different instance types available can be divided into several families, each with their unique characteristics. The most commonly used instance families are:
db.r6g: This family is designed for memory-intensive workloads, such as in-memory databases, high-performance computing, and data-intensive workloads.
db.t4g: This family is designed for low-cost, general-purpose workloads, including development and test environments, small-scale production workloads, and applications that don't require a lot of CPU power.
db.m6g: This family is designed for general-purpose workloads and is optimized for a balance of compute, memory, and network resources.
Selecting the appropriate initial size for your RDS or Aurora instance is crucial to ensure it can handle the expected workload. To do so, you should consider several factors, including the workload, traffic, and expected growth. AWS RDS and (Aurora instance types)[https://blog.guilleojeda.com/understanding-aws-aurora-instance-types?utm_source=blog&utm_medium=hashnode] and families can serve as a guide to select the right initial size for your workload.
For example, if you're expecting a moderate amount of read and write requests, with a moderate amount of data and simple queries, you can start with a (db.t4g.medium)[https://blog.guilleojeda.com/everything-you-need-to-know-about-aws-rds-instance-types?utm_source=blog&utm_medium=hashnode] instance type. If you're expecting a high amount of read and write requests, with a large amount of data and complex queries, you can start with a db.m6g.large instance type.
Once you have launched the instance, it's essential to monitor its performance using AWS RDS and Aurora performance metrics. These metrics, such as CPU utilization, memory usage, and I/O operations, can help you evaluate the instance's performance and identify when to resize.
Stop copying cloud solutions, start understanding them. Join over 45,000 devs, tech leads, and experts learning how to architect cloud solutions, not pass exams, with the Simple AWS newsletter.
Rightsizing your RDS or Aurora instance involves adjusting the resources to match the actual usage of your workload. This can include adjusting the CPU, memory, and storage of your instance to better match the needs of your application. Several methods can be used to identify when to rightsize, including:
Step 1: Go to the CloudWatch Console.
Step 2: Select the desired time range for your metrics.
Step 3: Locate your RDS or Aurora instance and select the "DBInstanceIdentifier"
Step 4: Check the metrics for CPU, Memory and Storage usage.
Step 5: Compare the usage with the current configuration of your instance and determine if there is an opportunity to rightsize.
Step 1: Go to the RDS or Aurora Console.
Step 2: Select your RDS or Aurora instance.
Step 3: Click on the "Performance Insights" button.
Step 4: Check the metrics for CPU, Memory and Storage usage.
Step 5: Compare the usage with the current configuration of your instance and determine if there is an opportunity to rightsize.
Step 1: Connect to your RDS or Aurora instance using SQL client.
Step 2: Run the following query: "SHOW STATUS WHERE variable_name = 'Threads_connected'"
Step 3: Check the value of the "Threads_connected"
Step 4: Compare the value with the current configuration of your instance and determine if there is an opportunity to rightsize.
By using a combination of these methods, you can gain a better understanding of the usage patterns of your RDS or Aurora instance and make informed decisions about when to rightsize.
Resizing your RDS or Aurora instance involves modifying its instance type or storage capacity. When resizing, it's important to keep downtime to a minimum to avoid impacting your application's availability and business continuity. To minimize downtime, you can take the following steps:
Step 1: Create a read replica of your RDS or Aurora instance in the same Availability Zone as the original instance.
Step 2: Verify that the read replica is in a "Ready" state.
Step 3: Promote the read replica to be a standalone database. This ensures that any data written to the original instance during the migration process is also available on the new instance.
Step 4: Modify the DNS entry or connection string of your application to point to the new primary instance.
Step 5: After the DNS change propagates, ensure that your application can successfully connect to the new instance.
Step 6: Test your application thoroughly to ensure that it works as expected.
Step 7: Finally, delete the original DB instance.
By following this process, you can resize your RDS instance with minimal downtime and without losing any data. However, it's important to note that there may still be a short period of downtime during the switch-over process, typically around 1-2 minutes. It's also a good idea to take a snapshot of your RDS instance before resizing it, in case you need to roll back the changes.
Choosing the right size for your AWS RDS or Aurora instance is crucial to ensure optimal performance and cost efficiency. By understanding the basics of instance types and families, picking the right initial size, identifying when to rightsize, and resizing with minimum downtime, you can optimize your database performance and reduce unnecessary costs. Remember to regularly monitor the performance of your instances and make adjustments as needed to keep your applications running smoothly.
Stop copying cloud solutions, start understanding them. Join over 45,000 devs, tech leads, and experts learning how to architect cloud solutions, not pass exams, with the Simple AWS newsletter.
Real scenarios and solutions
The why behind the solutions
Best practices to improve them
If you'd like to know more about me, you can find me on LinkedIn or at www.guilleojeda.com
