Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 8080fc1

Browse files
Merge pull request #2652 from splunk/urbiz-DG28141-spoc-aws
[DG28141]: SpOC Note
2 parents ef2234a + 7c47f2c commit 8080fc1

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

sp-oncall/spoc-integrations/aws-cloudwatch-integration-guide.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,12 +28,14 @@ them through some other means, such as email. If you need more information on ho
2828
Turn on AWS Cloudwatch in Splunk On-Call
2929
=============================================
3030

31-
In Splunk On-Call, select :guilabel:`Integrations`, :guilabel:`AWS CloudWatch`.
31+
In Splunk On-Call, select :guilabel:`Integrations`, :guilabel:`AWS CloudWatch`.
3232

3333
If the integration has not yet been activated, select :guilabel:`Enable Integration` to generate your endpoint URL. Be sure to replace the ``$routing_key`` section of your new endpoint with the routing key you want to use. If no routing key is included as part of the endpoint URL, the subscription isn't confirmed. See :ref:`spoc-routing-keys` for more information.
3434

3535
You can point multiple SNS subscriptions to the same AWS CloudWatch endpoint in Splunk On-Call. The subscription isn't confirmed if it hits a different endpoint.
3636

37+
.. note:: After you set it up, AWS automatically confirms the subscription after a few minutes.
38+
3739
Linking Splunk On-Call in AWS Simple Notification Service (SNS)
3840
=======================================================================
3941

0 commit comments

Comments
 (0)