Home Optimization & Allocation Cost Optimization Upgrade your AWS Redshift node type generation to optimize cloud cost

Upgrade your AWS Redshift node type generation to optimize cloud cost

-

Organizations use multiple instances of services such as day to day basis to support their daily operations. Users are highly dependent on the performance of their Redshift nodes to perform daily analytical and warehouse operations. Better optimization of Redshift node leads to better outputs. Hence it becomes necessary to make sure that your deployed Redshift node is of current generation which ensures cost savings as well as better performance of your cloud infrastructure.

Why Redshift node needs to be upgraded to the current generation to ensure better cloud performance?

Upgrading Redshift nodes to the current generation has various benefits. The latest generation of nodes ensure better hardware performance of CPU and leads to increased throughput of memory and network resources associated with Redshift nodes. Some bug fixes and new features also get provisioned as an add-on which further enhances performance and output. It is highly recommended to make sure that your instances are upgraded to latest generation whenever an upgrade for the same is available as the latest generation of nodes provides additional benefits and performance improvements at the same cost.

How does Centilytics come into the picture

Centilytics provides a dedicated insight based on AWS Redshift node type generation from a security standpoint. This insight allows users to take note of their Redshift nodes and ensure whether they are upgraded to the latest generation or not.

Insight descriptions

There can be 2 possible scenarios:

Severity Description
WarningWARNING This indication will be displayed when the corresponding Redshift node is of the previous generation and is not upgraded to the current generation.
OK This indication will be displayed when the corresponding Redshift node 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 Redshift node generation-ss2
  2. Region: This column shows the region in which the corresponding resource exists.AWS Redshift node generation-ss4
  3. Identifier: This column shows the ARN of the Redshift node. ARN is an identifier used by AWS to differentiate between different types of resources in your cloud infrastructure.AWS Redshift node generation-ss3
  4. Resource Name: This column shows the resource name or the instance name of your Redshift Node.AWS Redshift node generation-ss5
  5. Instance type: This column shows the type of Redshift node.AWS Redshift node generation-ss6
  6. Current Generation: This column shows the status whether your RDS instances are upgraded to current generation or not. ‘Yes’ will be displayed when the instance is of the latest generation. Otherwise, ‘No’ will be displayed.AWS Redshift node generation-ss1

 Filters applicable-

Filter Name Description
Account Id Applying the account Id filter will display data for the selected account Id.
Region Applying 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 environment 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 eg- If the user has tagged some resource by a tag named environment and has given it a value say production (environment: production), then the user will be able to view data of all the resources which are tagged as environment: production. User can use the tag value filter only when a tag name has been provided.

 

 

 

 

 

 

 

 

 

Read About

Cloud