Topics on this page
Amazon SNS Communication
Location | Main Dashboard > Select {Account} > Settings > Communication settings > Update communication settings > Configure 'Amazon SNS' |
Set up an Amazon SNS channel
- Click on Create an Amazon SNS channel
- Set automatic notifications
- Set manual notifications
-
Enter the Channel Name
The field is limited to 20 characters
-
Click Configure now requires a two-step process
-
Setup access
-
Setup KMS Key (Recommended)
-
Go to Key Management Service (KMS) in your AWS Console.
Note: If you already have a key, update your policy to allow key usage permission for AWS account: 717210094962, then proceed to Setup SNS Topic.
-
Click Customer managed keys and then Create key
- Enter the following details for Add alias and description step >> click Next
Alias: CloudConformitySNSEncryptionKey
Description: CloudConformitySNSEncryptionKey - On Add tags. step >> Add the tags >> click Next
- On Define key administrative permissions step >> Select a Key administrator >> click Next
- On Define key usage permissions step
Click Add another AWS account >> enter the AWS account id: 717210094962 >> Click Next - On Review and edit key policy step. Review the policy >> click Finish
-
-
Setup SNS Topic (Required)
- Create an SNS Topic (under the Simple Notification Service section in the AWS Console)
Topic Name: CloudConformity - Select your SNS topic >> click Edit
- Expand Encryption section >> select Enable encryption
Under Customer master key (CMK), clear the default aws key and select CloudConformitySNSEncryptionKey -
Expand Access policy >> update the following code >> add it as a new statement >> click Save changes
{ "Sid": "a unique statement ID", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::717210094962:root" }, "Action": "SNS:Publish", "Resource": "Your SNS Topic ARN" }
- Create an SNS Topic (under the Simple Notification Service section in the AWS Console)
-
-
Input SNS Topic ARN
-
SNS Notification Attributes
- failureDiscoveryDate : the date of failure discovery. A failure can be discovered either when the check was originally created or when a check status was updated from SUCCESS to FAILURE. Example: if a check is created today, "Failure discovery date" is set to today. If a check exists and was successful, but changed to a failure today, "Failure discovery date" is set to today.
- lastUpdatedDate : the timestamp of the last time Conformity Bot or RTM updated any attribute of the check.
- lastStatusUpdateDate : the timestamp of the last time Conformity Bot or RTM updated status attribute of the check. For new checks, this field is set to the creation date.
- lastModifiedBy : AWS Identity of the user that caused an event that RTM picked up and either created a new check in FAILURE status or updated an existing check with SUCCESS to FAILURE.
- lastModifiedDate: the timestamp of when lastModifiedBy is set.
FAQs
We currently have a python Slackbot that can alert each user directly. Does Cloud Conformity have a way to send alerts as SQS message so that it can be picked up by our Slackbot?
Yes, follow the steps below:
- Set up an Amazon SNS channel
- Subscribe to SNS and add SQS endpoint
Can integration be built into Atlassian OpsGenie?
OpsGenie has a native SNS integration. Therefore, notifications created in SNS will automatically be created in OpsGenie through the integration.