Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create a new SNS Topic and configure AWS Config Settings to send notifications to these newly created SNS topics
  2. Modify an existing SNS topic which are already setup to receive notification from AWS Config

...

  1. From SNS, create a topic with the following name: hypergrid-config-topic
  2. In the SNS topic wizard, under Access Policy configure the following:
    1. Define who can publish messages to the topic - Only the topic owner
    2. Define who can subscribe to the topic – select *Only requesters with certain endpoints  enter the endpoint ARN of HyperGrid SQS*
  3. Next, HyperGrid SRE will subscribe the HyperGrid SQS to the SNS topic created in this topic.

Modify an existing SNS topic for Config Stream
This topic describes the steps to modify the access policy of an existing SNS topic so HyperGrid SQS can subscribe to the SNS Topic. Use the following JSON policy allow HyperGrid SQS to subscribe to the SNS topic.
Note: This will be an ARN for the config-queue created on the HyperGrid AWS account and is also configured in the *HyperCloud™ Portal  System Settings * config.stream.sqs.arn for example: arn:aws:sqs:us-east-2:<<HyperGridAccountID>>:config-queue. Contact support@hypergrid.com in case this information is not available.

...

{
"Sid": "__console_sub_0",
"Effect": "Allow",
"Principal": {
"AWS": "*"
},
"Action": [
"SNS:Subscribe",
"SNS:Receive"
],
"Resource": "arn:aws:sns:us-east-1:<<CustomerAccountID>>:Customer-Config-Topic",
"Condition": {
"StringLike": {
"SNS:Endpoint": "arn:aws:sqs:us-west-2:<<HyperGridAccountID>>:HyperGrid-Config-Queue"
}
}
}

...