Fixed key under the canonical notifications section of
amplify_outputs.json where the notifications endpoint / region are surfaced
to the client (notifications.amazon_connect). This is the
exact path amplify-js reads in parseAmplifyOutputs (parseNotifications).
This is intentionally NOT configurable: every first-party Amplify Gen2
resource (defineAuth / defineData / defineStorage / defineFunction)
writes its backend output to a fixed, well-known key rather than a
caller-chosen one, so the client config contributors know where to read it.
This resource follows the same convention with a single stable key.
Fixed key under the canonical
notificationssection ofamplify_outputs.jsonwhere the notifications endpoint / region are surfaced to the client (notifications.amazon_connect). This is the exact path amplify-js reads inparseAmplifyOutputs(parseNotifications).This is intentionally NOT configurable: every first-party Amplify Gen2 resource (
defineAuth/defineData/defineStorage/defineFunction) writes its backend output to a fixed, well-known key rather than a caller-chosen one, so the client config contributors know where to read it. This resource follows the same convention with a single stable key.