Deferred maintenance should be enabled for all your AWS Redshift clusters in order to keep your data warehouse running without interruption during critical business periods. Amazon Redshift service gives you the option to defer maintenance for your clusters by up to 14 days.
User activity logging should be enabled for your Amazon Redshift clusters for troubleshooting purposes.
Idle AWS Redshift clusters should be terminated in order to help lower the cost of your monthly AWS bill.
The automated snapshot retention period set for your AWS Redshift clusters should be a positive number, meaning that automated backups are enabled for the clusters.
Version Upgrade should be enabled for Redshift clusters to automatically receive upgrades during the maintenance window.
Audit logging should be enabled for Redshift clusters for security and troubleshooting purposes.
AWS Redshift database clusters should not be using "awsuser" (default master user name) for database access.
Amazon Redshift clusters should not be using port 5439 (default port) for database access.
Database encryption should be enabled for AWS Redshift clusters to protect your data at rest.
Redshift clusters should be encrypted with KMS customer master keys (CMKs) in order to have full control over data encryption and decryption.
Your Redshift clusters should be provisioned within the AWS EC2-VPC platform instead of EC2-Classic platform (outdated) for better flexibility and control over clusters security, traffic routing, availability and more.
Amazon Redshift clusters should not be publicly accessible in order to minimise security risks.
Your existing Amazon Redshift cluster nodes should have the desired type established by your organization based on the workload deployed.
AWS Redshift clusters with high disk usage should be scaled to increase their storage capacity.
Redshift clusters should be using the latest generation of nodes for performance improvements.
Your AWS account should not have reached the limit set for the number of Redshift cluster nodes.
AWS Redshift non-default parameter groups require SSL to secure data in transit.
Amazon Redshift Reserved Nodes (RN) should be renewed before expiration.
Amazon Redshift Reserved Nodes (RN) should be renewed before expiration.
Ensure that none of your AWS Redshift Reserved Node purchases have been failed.
Ensure that none of your AWS Redshift Reserved Node purchases are pending.
Ensure Redshift Reserved Node purchases are regularly reviewed for cost optimization (informational).
Underutilized Redshift clusters should be downsized in order to optimize AWS costs.
Ensure that your Amazon Redshift Reserved Nodes are being utilized.
If you are not yet convinced to sign up with Cloudanix, that's not a problem. We recommend you use a comprehensive checklist which your team can use to perform a manual assessment of your workload.