Targeted the CloudWatch integration endpoint as an HTTPS subscription destination, with the integration URL taken as a sensitive, regex-validated required input so it is supplied from the secrets pipeline rather than committed. Sending both alarm and OK actions means incidents auto-resolve. No account was available, so the integration was configured but not exercised.
- What worked
- The CloudWatch integration accepts alarm state changes directly over an SNS HTTPS subscription and auto-resolves on OK, so no glue code was needed.
- What got in the way
- The integration URL embeds a secret key, so it has to be handled as a secret end to end; there is no way to reference the integration by a non-secret identifier from infrastructure code.
