Home Uncategorized AWS RDS cluster limit – Control your usage before service limits breach

AWS RDS cluster limit – Control your usage before service limits breach

-

Users need to be aware of their AWS RDS cluster limit for they can create in a particular region to make sure they have control over their usage before breaching limits. Service limits, if taken care of, can provide high availability and robust performance levels to your cloud infrastructure.

Why users need to be aware of their AWS RDS cluster limits?

Amazon RDS provides cost-efficient and resizable database capacity in the relational database which is of industry standards and also manages common database administration operations. An AWS RDS cluster is a collection of similar multiple RDS instances. You can use instances in a cluster for ‘read’ or ‘write’ operations. The configuration of database instances can, however, be changed according to the user’s requirement.

The default limit set for creating RDS clusters in a particular region via an AWS account is 40. There can be a situation where the user is creating clusters in a region without thinking of the cluster limit. If that limit is reached, further calls to create a cluster would fail with an exception. Breaching the limit defined for RDS clusters can also degrade the performance and health levels of your infrastructure.

How does Centilytics help you?

Centilytics has a dedicated insight that tells you about your RDS cluster limit and gives warnings whenever the cluster limit is about to be exhausted.

Insight descriptions:

There can be 3 possible scenarios:

Severity Description
CRITICAL This indication will be displayed when the user has breached 100% of the specified limit of the corresponding resource.
WARNING This indication will be displayed when the user has breached 80% of the specified limit of the corresponding resource.
OK This indication will be displayed when the user has breached less than 80% of the specified limit of the corresponding resource.

 

Description of further columns are as follows:

  1. Account Id: This column shows the respective account ID of the user’s account.AWS RDS ss1
  2. Account Name: This column shows the corresponding account name to the user’s account.AWS RDS ss2
  3. Region: This column shows the region in which the corresponding resource exists.AWS RDS ss3
  4. Limit Amount: This column shows the limit of the resource which is available. Here, the limit refers to the number of RDS clusters allowed to be created in a particular region.AWS RDS s3
  5. Current usage: This column shows the current usage level of the corresponding resource.AWS RDS ss666
  6. Service: This column shows the type of service limit.AWS RDS s555

Compliances covered:

Compliance Name Reference No. Link
Trusted Advisor https://console.aws.amazon.com/trustedadvisor/home?#/category/service-limits

 

Filters applicable:

Filter Name Description
Account Id Applying the account Id filter will display all the resources for the selected account Id.
Region Applying the region filter will display all the resources corresponding to the selected region.
Severity Applying severity filter will display the resources according to the selected severity type i.e. selecting critical will display all resources with critical severity. Same will be the case for Warning and OK severity types.

 

Read More:

Latest guide on Amazon Relational Database Service Limits

Cloud

Cloud Management