Allow use of SNS topics for AWS Amplify Build Notifications

[jeffscottlevine]

Is your feature request related to a problem? Please describe. The AWS Amplify console allows the submission of e-mail addresses to receive build notifications. After an address is entered, an SNS topic is created and the e-mail address is subscribed to it. It is not possible to specify an existing SNS topic.

Describe the solution you'd like I would like to see the Amplify console allow the use of existing SNS topics for build notifications.

Additional context None.

[mtheoryx]

Or alternatively (if it helps speed up development)...

If it were possible to list or export the ARN for whatever topic is already being created "behind the scenes", it could allow other non-amplify integrations by subscribing to that topic.

Given:

• There is an SNS topic being created via actions in the Console (by opting into build notification emails)
• The topic appears to be tied (with naming) to Source Control Branch connection (main/dev/feature)
• The topic(s) are findable via Console -> SNS (check region)
• The ARN is listed for that topic

Would be great if Amplify could:

• Create this topic from the CLI (instead of just the Console)
• List the topic from the CLI
• Display the topic as a backend environment UI (stretch goal)

To then allow me to create new integrations such as:

• Use IoT devices to illuminate/display the build status of an amplify deployment
• Integrate with a Streamdeck or other webhook based service (Zapier) to display build/deploy status
• Notify of failure to a text message via Twilio (or other)
• Write results to a custom location (S3, SIEM, Etc)

If the above narrows down the scope of the request, hopefully, I would love to hear other input on how this might be valuable.

[diogokawamoto]

Inspecting which resources are created when I setup the email notification, I found the following event pattern for EventBridge.

I think it is possible to set a SNS topic as target for this event.

{
  "detail": {
    "appId": ["<amplify-app-id>"],
    "branchName": ["main"],
    "jobStatus": ["SUCCEED", "FAILED", "STARTED"]
  },
  "detail-type": ["Amplify Deployment Status Change"],
  "source": ["aws.amplify"]
}