Module types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS User Notifications can respond with.

Structs

• AggregationDetail

  Provides detailed information about the dimensions used for aggregation.

• AggregationKey

  Key-value collection that indicate how notifications are grouped.

• AggregationSummary

  Provides additional information about the aggregation key.

• Dimension

  The key-value pair of properties for an event.

• EventRuleStatusSummary

  Provides additional information about the current EventRule status.

• EventRuleStructure

  Contains a complete list of fields related to an EventRule.

• ManagedNotificationChannelAssociationSummary

  Provides a summary of channel associations for a managed notification configuration.

• ManagedNotificationChildEvent

  A ManagedNotificationChildEvent is a notification-focused representation of an event. They contain semantic information used to create aggregated or non-aggregated end-user notifications.

• ManagedNotificationChildEventOverview

  Describes an overview and metadata for a ManagedNotificationChildEvent.

• ManagedNotificationChildEventSummary

  Describes a short summary and metadata for a ManagedNotificationChildEvent.

• ManagedNotificationConfigurationStructure

  Describes the basic structure and properties of a ManagedNotificationConfiguration.

• ManagedNotificationEvent

  A notification-focused representation of an event. They contain semantic information used by AccountContacts or Additional Channels to create end-user notifications.

• ManagedNotificationEventOverview

  Describes an overview and metadata for a ManagedNotificationEvent.

• ManagedNotificationEventSummary

  A short summary of a ManagedNotificationEvent. This is only used when listing managed notification events.

• ManagedSourceEventMetadataSummary

  A short summary and metadata for a managed notification event.

• MediaElement

  Describes a media element.

• MessageComponents

  Describes the components of a notification message.

• MessageComponentsSummary

  Contains the headline message component.

• NotificationConfigurationStructure

  Contains the complete list of fields for a NotificationConfiguration.

• NotificationEventOverview

  Describes a short summary of a NotificationEvent. This is only used when listing notification events.

• NotificationEventSchema

  A NotificationEvent is a notification-focused representation of an event. They contain semantic information used by Channels to create end-user notifications.

• NotificationEventSummary

  Describes a short summary and metadata for a NotificationEvent.

• NotificationHubOverview

  Describes an overview of a NotificationHub.

  A NotificationConfiguration is an account-level setting used to select the Regions where you want to store, process and replicate your notifications.

• NotificationHubStatusSummary

  Provides additional information about the current NotificationHub status.

• NotificationsAccessForOrganization

  Orgs Service trust for User Notifications.

• Resource

  A resource affected by or closely linked to an event.

• SourceEventMetadata

  Describes the metadata for a source event.

  For more information, see Event structure reference in the Amazon EventBridge User Guide.

• SourceEventMetadataSummary

  Contains metadata about the event that caused the NotificationEvent. For other specific values, see sourceEventMetadata.

• SummarizationDimensionDetail

  Provides detailed information about the dimensions used for event summarization and aggregation.

• SummarizationDimensionOverview

  Provides an overview of how data is summarized across different dimensions.

• TextPartValue

  Describes text information objects containing fields that determine how text part objects are composed.

• ValidationExceptionField

  Stores information about a field passed inside a request that resulted in an exception.

Enums

• AccessStatus
  When writing a match expression against AccessStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AccountContactType
  When writing a match expression against AccountContactType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AggregationDuration
  When writing a match expression against AggregationDuration, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AggregationEventType
  When writing a match expression against AggregationEventType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ChannelAssociationOverrideOption
  When writing a match expression against ChannelAssociationOverrideOption, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ChannelType
  When writing a match expression against ChannelType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EventRuleStatus
  When writing a match expression against EventRuleStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EventStatus
  When writing a match expression against EventStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LocaleCode
  When writing a match expression against LocaleCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• MediaElementType
  When writing a match expression against MediaElementType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• NotificationConfigurationStatus
  When writing a match expression against NotificationConfigurationStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• NotificationHubStatus
  When writing a match expression against NotificationHubStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• NotificationType
  When writing a match expression against NotificationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SchemaVersion
  When writing a match expression against SchemaVersion, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• TextPartType
  When writing a match expression against TextPartType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ValidationExceptionReason
  When writing a match expression against ValidationExceptionReason, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.