Using ElastiCache clusters with the latest version of Redis cache engine you will benefit from new features and enhancements, better performance, better memory management, bug fixes and security patches. In order to adhere to AWS best practices, update your Amazon ElastiCache Redis cluster to stable latest engine version.
Notifies about AWS Auto Scaling Group (ASG) health check feature is properly configured. By using the right health check configuration for your Auto Scaling Groups, you can increase the reliability and availability of the applications deployed within these groups. If an AWS Elastic Load Balancer (ELB) is being used make sure that the ELB health check is enabled and If an Elastic Load Balancer is not being used within your ASG make sure that the EC2 health check is enabled
Workflow to report whether any AWS Workspaces are in an 'Unhealthy State'. Report is sent once every day, and can be configured according to the use case.
Reports all the ACM Certificates which have Wildcard Domain Names.
It is an AWS best practice to launch every EC2 machine in an AWS Auto Scaling Group to achieve zero downtime. This workflow sends a report of instances not launched in an auto-scaling group.
It is an AWS best practice to stop and relaunch your old EC2 instances, so that they are reallocated to updated and more reliable hardware. Instances older than 150 days are recommended to be updated.
It is AWS best practice to enable automated backups for your Redshift cluster so that in case of unexpected failures data can be recovered
Checks whether Auto Scaling Groups have Elastic Load Balancers associated with them. In the case of a failure of any of the EC2 resources, the presence of Elastic Load Balancers will ensure availability. Runs every Monday, Wednesday and Friday.
Check whether Auto Scaling Group notifications are configured to send e-mail notifications. It's useful to get e-mail notifications when a important event such as a scaling event (Eg: launching an instance) occurs.
Identify Auto Scaling Groups that are not using appropriate cooldown periods, every hour. This helps you to ensure that one scaling event is not initiated before the effects of another are evident.