A container workload in an EKS cluster uses Amazon Managed Service for Prometheus for monitoring. The DevOps team wants alerts to be sent to an SNS topic in the same account. Which combination of steps is required? (Choose three.)

To send alerts from Amazon Managed Service for Prometheus (AMP) to an SNS topic, you first need to define what to alert on. This is done by creating alerting rules that specify conditions, such as container availability. Next, you need a mechanism to process these alerts and send them to SNS. AMP integrates with Alertmanager for this purpose, so you must create an Alertmanager configuration that defines the SNS topic as a receiver. Finally, for AMP's Alertmanager to publish messages to the SNS topic, the SNS topic's access policy must explicitly grant sns:Publish and sns:GetTopicAttributes permissions to the aps.amazonaws.com service principal, which is the service principal for AMP. Incorrect options: Using the Managed Service for Prometheus remote write URL is for sending metrics to Prometheus, not for sending alerts from Prometheus. Modifying the IAM role used by Managed Service for Prometheus is not the correct way to grant permissions for SNS publishing; the SNS topic policy controls who can publish to it. Creating an OIDC provider and service account is relevant for EKS workloads accessing AWS services, but not directly for AMP's Alertmanager sending alerts to SNS.