Cloud service · AWS · Updated

AWS User Notifications - AWS User Notifications centrally configures and displays notifications from AWS services and delivers them through supported notification channels.

In short

AWS User Notifications helps engineers collect selected AWS service events in a notification center and route them to email, chat, or mobile push destinations. It supports event filtering and aggregation so teams can receive relevant operational updates without building a separate notification pipeline for every service.

Cloud Services Hub →

8 key features of AWS User Notifications

01
Central notification center

Review notifications from AWS services in a common AWS Management Console interface. This gives engineers a consolidated view without requiring them to inspect each service console separately.

02
Event-based notification configurations

Create configurations that select service events and associate them with delivery destinations. Separate configurations by workload, environment, or operational team to keep routing understandable.

03
Event filtering

Narrow notifications using supported event attributes rather than forwarding every event from a service. Validate filters against the source service's EventBridge event schema.

04
Multiple delivery channels

Send notifications to verified email contacts, supported chat destinations, and the AWS Console Mobile Application. Configure and authorize each destination before relying on it for operational communication.

05
Notification aggregation

Combine related events to reduce repeated messages during bursts of activity. Balance lower notification volume against the delay introduced by aggregation.

06
Regional event selection

Select the supported AWS Regions whose events a configuration should monitor. Explicit regional selection helps prevent coverage gaps for workloads deployed outside a team's primary Region.

07
Notification hubs

Configure notification hubs to establish where notification data is stored and processed. Include hub placement in regional availability and data residency reviews.

08
Programmatic administration

Use AWS APIs and SDKs to manage notification configurations, event rules, and channel associations. Manage email contacts through the AWS User Notifications Contacts API and restrict administrative actions with IAM.

Where AWS User Notifications is used

  1. 01
    CloudWatch alarm awareness

    Notify an operations team when selected CloudWatch alarms change state. Filter for actionable transitions and route them to the team's email or chat destination.

  2. 02
    Infrastructure state monitoring

    Send notifications when selected EC2 instances change state. Use resource-aware filters to distinguish production workload changes from expected development activity.

  3. 03
    AWS Health event communication

    Route relevant AWS Health events to engineers responsible for affected workloads. Review event details and affected resources before deciding whether operational action is necessary.

  4. 04
    Reducing notification bursts

    Aggregate related events generated during fleet updates or deployments. This keeps shared destinations readable while retaining access to notification details.

  5. 05
    Mobile operational visibility

    Deliver selected notifications through the AWS Console Mobile Application for engineers working away from a desktop. Use a separate escalation system when acknowledgement or on-call scheduling is required.

How AWS User Notifications is priced

No additional service charge

AWS User Notifications is available at no additional charge. Creating notification configurations and using its supported notification delivery capabilities does not introduce a separate User Notifications usage fee.

Associated service charges

Normal charges can still apply to services used alongside the notification workflow, such as CloudWatch alarms, custom EventBridge processing, or automated remediation. Evaluate those resources independently rather than assuming the entire monitoring architecture is free.

Services AWS User Notifications works with

A common architecture starts with an AWS service emitting an operational event to Amazon EventBridge. AWS User Notifications selects supported events through its event rules, applies configured filters, and delivers the resulting notifications to associated channels. For example, CloudWatch evaluates an application latency metric, emits an alarm state change, and User Notifications routes the selected transition to an operations destination.

Infrastructure and service-health notifications follow a similar pattern. EC2 state-change events can identify unexpected instance shutdowns, while AWS Health events communicate relevant service issues or scheduled changes. Separate configurations by ownership and urgency so that a development instance transition does not reach the same audience as a production health event. Apply aggregation where bursts of related activity would otherwise overwhelm recipients.

For collaboration, associate supported chat destinations through Amazon Q Developer in chat applications, formerly AWS Chatbot, or use verified email contacts and mobile push channels. Keep automated actions on a separate path: EventBridge rules can invoke remediation workflows independently of human notification delivery. This separation allows engineers to adjust communication settings without changing remediation behavior and avoids making operational automation depend on someone receiving or reading a notification.

Amazon EventBridgeAmazon EventBridge

AWS User Notifications uses EventBridge events to select supported AWS service activity. For example, an event rule can match a particular service event and apply additional filtering before creating a notification. Use the source event schema when defining filters; an arbitrary custom event bus should not be assumed to be a supported notification source.

Amazon CloudWatchAmazon CloudWatch

CloudWatch evaluates metrics and produces alarm state-change events that can drive User Notifications. For example, notify a workload channel when a production latency alarm enters the ALARM state. Keep thresholds and evaluation periods in CloudWatch, and manage notification selection and delivery in User Notifications.

AWS Health DashboardAWS Health Dashboard

AWS Health events can inform teams about service issues and changes relevant to their AWS resources. For example, route applicable scheduled-change events to the infrastructure team's email destination. Event availability and detail depend on the AWS Health event and account context.

Amazon EC2Amazon EC2

EC2 instance state-change events can be selected for operational notifications. For example, alert a team when a specific production instance transitions to stopped or terminated. Filter for relevant instance identifiers and states to avoid notifications for routine development activity.

AWS ChatbotAWS Chatbot

Supported chat configurations provide delivery destinations for AWS User Notifications. For example, associate a notification configuration with a configured Slack or Microsoft Teams channel used by the operations team. Establish the chat integration and required permissions before associating the destination.

Amazon API GatewayAmazon API Gateway

AWS User Notifications can notify you about API Gateway configuration changes by matching CloudTrail API events in EventBridge, such as an API deployment or stage deletion.

Amazon AppFlowAmazon AppFlow

AWS User Notifications can turn AppFlow flow-execution events in EventBridge into notifications, including alerts when a data transfer fails.

Amazon AthenaAmazon Athena

AWS User Notifications can notify you when Athena queries change state by matching Athena events in EventBridge, for example when a query fails.

Amazon Augmented AI (Amazon A2I)Amazon Augmented AI (Amazon A2I)

AWS User Notifications can deliver notifications for Amazon A2I human-loop state changes published to EventBridge, such as a human review completing or failing.

Amazon AuroraAmazon Aurora

AWS User Notifications can surface Aurora database events delivered through Amazon RDS to EventBridge, including failovers and changes to database availability.

AWS User Notifications exam questions

Real practice exam questions on AWS User Notifications, with the correct answer and its explanation. Answer them with every option in the exam simulator.

DVA-C02

A company has Amazon CloudWatch alarms that monitor AWS Lambda concurrency utilization. Developers currently inspect the alarms manually. The team wants an email whenever a selected alarm transitions to ALARM and wants to review the resulting notifications in a centralized AWS Management Console notification center. Transitions to OK or INSUFFICIENT_DATA must not generate notifications. The solution must use managed event filtering without custom code.

Which solution meets these requirements with the least operational effort?

Show answerCORRECT ANSWER

Create an AWS User Notifications configuration for CloudWatch alarm state-change events. Filter for the selected alarms and a new state of ALARM, and associate a verified email delivery destination.

AWS User Notifications can filter CloudWatch alarm state-change events for the selected alarms entering ALARM. It makes the resulting notifications available in the console notification center and can deliver them to verified email destinations without custom processing code.

Practice AWS User Notifications in a full exam

Questions on AWS User Notifications in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is AWS User Notifications

3 min read

AWS User Notifications provides a central place to configure and view notifications about activity in an AWS environment. It is intended for human-facing operational notifications, such as changes to infrastructure state, CloudWatch alarm transitions, and AWS Health events. Engineers can review notifications in the AWS Management Console and configure additional delivery channels for recipients who do not continuously monitor the console.

The main configuration resource is a notification configuration. It defines which events should produce notifications and how those notifications should be delivered. Event rules select an AWS service, an event type, and the AWS Regions to monitor. Additional filtering can narrow the selection to relevant resources or event attributes. For example, an operations team can select EC2 instance state-change events and filter for instances entering a stopped state rather than receiving every instance transition.

The service distinguishes user-configured notifications, generated by configurations you create, from AWS managed notifications, generated by default. AWS Health, AWS Marketplace, and AWS Billing and Cost Management send AWS managed notifications through User Notifications.

Notification configuration quotas are not adjustable: an account can have at most 50 configurations overall, 20 for a specific service, and 10 for a specific service and event type.

The service uses Amazon EventBridge events to support event selection. This makes the source service's event schema important: filters must match the fields and values actually emitted by that service. Before enabling broad delivery, inspect representative events and test the configuration against a controlled change. A filter that does not match the event payload can silently exclude the operational activity the team intended to monitor.

The maximum source-event rate is one event per second per AWS account, and this quota is not adjustable.

Supported delivery options include email, chat channels through Amazon Q Developer in chat applications, formerly AWS Chatbot, and push notifications through the AWS Console Mobile Application. Delivery destinations require the appropriate setup and authorization. Email contacts must complete verification before they can receive notifications. Choose destinations according to the audience and sensitivity of the notification rather than sending every event to a shared channel.

Aggregation combines related events into fewer notifications. This is useful during deployments, fleet changes, or incidents that generate many similar events. Select aggregation settings according to operational urgency: reducing message volume is helpful, but a longer aggregation interval can delay when recipients see an individual event.

Notification hubs identify Regions where notification data is stored and processed. Configure hubs deliberately, taking supported Regions and data residency requirements into account. Use IAM permissions to control who can create notification configurations, change event rules, and associate delivery channels.

Notification hubs and notification configurations apply only to user-configured notifications. Receiving these notifications requires choosing at least one notification hub and then creating notification configurations.

AWS User Notifications complements monitoring and incident-management systems; it does not replace them. Keep metric evaluation in CloudWatch, automated remediation in services such as EventBridge and Systems Manager, and escalation workflows in a dedicated incident-management system when acknowledgement and on-call scheduling are required. Treat notification delivery as an operational communication mechanism rather than a transactional message bus or an application messaging API.

AWS architecture icons are the property of Amazon Web Services. BlowStack is not affiliated with or endorsed by AWS.