Aurora Serverless v2 doesn't go back to 0.5 ACUs even when there is no activity on the database
We are observing consistently that the v2 serverless doesn't fall back to 0.5 ACUs when there is no activity on the database. It stays at 1.5-2 leading to 3 times the cost. I have attached two charts from Monitoring tab
- ACUS
- Database connections
As we can observe even when there are 0 connections, the ACUs stay high ARN of RDS instance: db-cluster-4.cluster-cjpydjcv1v6a.us-east-1.rds.amazonaws.com Database Endpoint: db-cluster-4.cluster-cjpydjcv1v6a.us-east-1.rds.amazonaws.com
ACU-configuration
ACUs-last-12-hours
db-connections-last-12-hours
- 最新
- 投票最多
- 评论最多
We have already read this and performance monitoring / performance insight is already disabled from our end.
There could be other features that consume memory. They might not set a lower bound on the ACUs when used individually, but in combination might take up enough memory to cause scaling. Are there any options you turned on when creating this cluster (e.g. IAM) or in PostgreSQL after setting up the cluster (e.g. logical replication)? Global database (the "Add Region" action in the console) is another one that's documented as requiring a minimum number of ACUs (8).
相关内容
AWS 官方已更新 2 年前
