how to choose rds when migrate rds from serverless v1?

Question

With past 2 years, we use serverless v1 rds , set min=max=2 acu. Our data size (2G) and access data are very small. 
for serverless v1 rds, our monthy cost ~ 86$. 
1) if we upgrade to serverless v2,  Is acu cost simialr between serverless v1 and serverless v2? 
2) how about change to use singal PostgreSQL rds?   I created one it report estimate as db.t3.medium,  ~55$/month
3) or how about change to Regional cluster with only writer instance (db.t3.medium) ? is this solution cost simiar as single db.t3.medium?

re:Post Agent · Answer

When migrating from Aurora Serverless v1 to another RDS option, there are several factors to consider:

1) Upgrading to Aurora Serverless v2:
The pricing structure between Serverless v1 and v2 is different. In Serverless v2, 1 ACU is equivalent to 2 GiB of memory. Given your current usage of 2 ACU in v1, you might set a minimum of 0.5 ACU and a maximum of about 2 ACU in v2 to handle slight load increases. The cost for 1 ACU in v2 is around $0.12 per hour in the Northern Virginia region. If you consistently use 0.5 ACU for a month without scaling, it would cost approximately $43, not including storage fees. With storage, it might be around $54 per month. This could potentially be more cost-effective than your current setup.

2) Changing to a single PostgreSQL RDS instance:
Your estimate for a db.t3.medium instance at about $55/month seems reasonable. This could indeed be a more cost-effective option compared to your current Serverless v1 setup, especially given your small data size and low access patterns. However, keep in mind that you'll lose the automatic scaling capabilities of Serverless.

3) Changing to a Regional cluster with only a writer instance:
A Regional cluster with a single db.t3.medium writer instance would likely have a similar cost to a single db.t3.medium instance. The main difference is that a Regional cluster allows you to add read replicas in the future if needed, providing more flexibility for potential growth.

Given your small data size and low access patterns, moving to a single PostgreSQL RDS instance or a Regional cluster with a single writer instance could potentially provide cost savings compared to your current Serverless v1 setup. However, you should carefully consider your specific needs, such as the importance of automatic scaling and potential future growth, when making your decision.

Remember to thoroughly test any migration plan before implementation to ensure it meets your performance and cost requirements.
      
**Sources**  
[Moving aurora Serverless instance to rds Provisoned | AWS re:Post](https://repost.aws/questions/QUpwwKm54WREqgaHOT4Qmafw/moving-aurora-serverless-instance-to-rds-provisoned)  
[Moving from RDS to Serverless | AWS re:Post](https://repost.aws/questions/QUfBuzBVtfQHKsG6-Uo5x1uA/moving-from-rds-to-serverless)

how to choose rds when migrate rds from serverless v1?

Relevant content