Home Optimization & Allocation Cost Optimization Why you need to upgrade your AWS RDS Instance right now?

Why you need to upgrade your AWS RDS Instance right now?


Organizations use multiple instances of services such as EC2, RDS on day to day basis to support their daily operations. Users are highly dependent on the performance of their EC2, RDS instances. Better optimization of resources leads to better outputs. Hence it becomes necessary to make sure that resources deployed are of the current generation. Upgrading your AWS RDS instance generation ensures cost savings as well as better performance of your cloud infrastructure.

What is RDS?

RDS is a web service interface that allows users to set up and operate the relational database in the cloud. A DB instance is the basic building block of RDS which can contain multiple databases created by the user. RDS instance is an isolated database infrastructure in the cloud. One RDS instance can contain multiple databases created by the users which can be accessed using the same tools that are used with stand-alone database instances.

Why AWS RDS instances should be upgraded to the current generation?

Upgrading RDS resources to the current generation has various benefits. Upgrading to the latest generation of instances helps in reducing cloud expenditure and also provides more computing capacity. The latest generation of instances ensure better hardware performance of CPU and leads to increased throughput of memory and network resources associated with RDS instances. Some bug fixes and new features also get provisioned as an add-on which further enhances the performance and output of your RDS instances. It also provides better support for the latest DB engines to be associated with an instance. It is highly recommended that you should upgrade your instances to the latest generation whenever an upgrade for the same is available.

Centilytics comes into the picture

Centilytics provides a dedicated insight into your AWS RDS instance generation. This insight lists down all the RDS instances which are running in the old generation and recommends you to upgrade them to the latest generation.

Insight descriptions:

There can be 2 possible scenarios:

Severity Description
 WARNING This indication will be displayed when the corresponding RDS instance is of the previous generation and is not upgraded to the current generation.
OK This indication will be displayed when the corresponding RDS instance is upgraded to the latest generation.

Description of further columns are as follows:

  1. Account Id: This column shows the respective account ID of the user’s account.

AWS RDS instance generation-ss2

  1. Region: This column shows the region in which the corresponding RDS instance exists.AWS RDS instance generation-ss5
  2. Identifier: This column shows the ARN of the RDS instance. ARN is an identifier that AWS uses to differentiate between different types of resources in cloud infrastructure.AWS RDS instance generation-ss3
  3. Resource Name: This column shows the resource name or the instance name of your RDS instance.AWS RDS instance generation-ss4
  4. Instance type: This column shows the type of RDS instance.AWS RDS instance generation-ss6
  5. Current Generation: This column shows the status of your RDS instances; whether you have upgraded them to the current generation or not. ‘Yes’ will be displayed when the instance is of the latest generation. Otherwise, ‘No’ will be displayed.  AWS RDS instance generation-ss1                

Filters applicable:

Filter Name Description
Account Id Applying account Id filter will display data for the selected account Id.
Region Applying the region filter will display data according to the selected region.
Severity Applying severity filter will display data 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
Resource Tags Applying resource tags filter will display those resources which have been assigned the selected resource tag. For eg: If the user has tagged some resource by a tag named environment, then selecting it from the resource tags filter will display all the resources with tag name-environment.
Resource Tags Value Applying resource tags value filter will display data which will have the selected resource tag value. For e.g. – Let’s say a user has tagged some resource by a tag named environment and has a value say production (environment: production). Hence, the user can view data of all the resources which are tagged as “environment:production”. The user can use the tag value filter only when a tag name has been provided.

This article is originally published at https://www.cloudmanagementinsider.com/upgrading-aws-rds-instance-generation-for-cost-optimization/

Read About