New serverless pattern - API Gateway - Amazon Connect Integration - #3287
Open
vaidehip86 wants to merge 1 commit into
Open
New serverless pattern - API Gateway - Amazon Connect Integration#3287vaidehip86 wants to merge 1 commit into
vaidehip86 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds the
apigw-connect-notificationpattern: an API Gateway sends in-app push notifications to Amazon Connect agents and admins through a direct AWS service integration via CreateNotification API.Level: 200
Framework: SAM
Services: API Gateway, Amazon Connect
What is Amazon Connect Notifications?
In-app notifications are on-screen alerts in the Amazon Connect workspace header. They're the only built-in mechanism to broadcast messages to agents/admins regardless of what page they're on. Currently Notifications can only be sent via the API — there is no console UI to compose or send them.
Supported use cases:
System notifications: availability impacts, failover events, policy changes, critical feature updates
Custom organizational messages: training reminders, schedule adherence alerts, emergency notifications
How it works
A
POST /notificationsREST endpoint accepts a JSON body with recipients, localized content, and optional priority/TTL.API Gateway transforms the request via a VTL mapping template (camelCase → PascalCase) and calls the Connect
CreateNotificationAPI directly using aPUTintegration.An IAM role grants API Gateway the
connect:CreateNotificationpermission. No Lambda function sits in between.Notifications appear in the Connect header for targeted users within seconds.