MSK clusters should have enhanced monitoring configured
Description
This control checks whether an Amazon MSK (Managed Streaming for Apache Kafka) cluster has enhanced monitoring configured. The specific requirement is that the monitoring level must be at least PER_TOPIC_PER_BROKER. The control will fail if the monitoring level for the cluster is set to DEFAULT or PER_BROKER. This monitoring level provides more granular insights into the performance of the MSK cluster. It offers metrics related to resource utilization, such as CPU and memory usage. This detailed visibility helps in identifying performance bottlenecks and resource utilization patterns for individual topics and brokers, which in turn can be used to optimize the performance of Kafka brokers.
Remediation
To remediate MSK clusters without enhanced monitoring, you need to enable CloudWatch Logs for the cluster.
Steps
- Navigate to the Amazon MSK console
- Select the MSK cluster that needs remediation
- Click on 'Edit' or 'Modify' cluster
- Go to 'Monitoring' settings
- Enable 'CloudWatch Logs'
- Configure log groups and retention settings
- Set up monitoring level to PER_TOPIC_PER_BROKER
- Review the monitoring configuration
- Apply the changes to the cluster
- Verify enhanced monitoring is working