You can spin up multiple instances in AWS Redshift for your daily operations. Hence it becomes necessary to make sure that resources deployed are optimized in terms of cost and utilization as well.
AWS Redshift cost optimization
AWS users should be aware of the no. of nodes that are available for use, in a particular Redshift cluster. If the user crosses this limit, then it can lead to an unnecessary increase in your AWS bill with respect to that user.
How can Centilytics help in cost optimization?
Centilytics provides an insight which gives warnings whenever the user has breached their Redshift node limit. This allows the users to take note of the same and act accordingly.
There can be only 1 possible scenario:
|Warning||This indication will be displayed when the corresponding Redshift cluster’s node limit is about to be breached.|
Description of further columns are as follows:
- Account Id: This column shows the respective account ID of the user’s account.
- Account Name: This column shows the corresponding account name to the user’s account.
- Region: This column shows the region in which the corresponding resource exists.
- Identifier: This column shows the name of the redshift cluster.
|Account Id||Applying the account Id filter will display all 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 resources according to the selected severity type i.e. selecting critical will display all instances 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 e.g., A user has tagged some public snapshots by a resource tag named environment. Then selecting an environment from the resource tags filter will display all those resources tagged by the 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 have “environment:production” tag assigned. The user can use the tag value filter only when a tag name has been provided.