Ascendon Configuration is where you set up listener details to start receiving data in Xponent (Region Endpoint) and IAM Role ARN. These configurations connect Ascendon to the Listener, allowing it to securely send real-time event data to the appropriate AWS environment.
Log in to Ascendon Invision using your assigned credentials.
Click on the people icon in the top-left corner of the page and select Configuration. It will navigate you to the AWS Credentials section of the configuration interface.
AWS Credential
An AWS credential in Ascendon is a secure configuration that allows the platform to connect to your AWS Kinesis stream.
Search for AWS Credentials using the search bar and select it. This will navigate you to the AWS Credentials window. and can be used while mapping the event notification kinesis.
Each hub typically uses its own credentials. If your hub already has a configured credential, there’s no need to add a new one unless you’re working in a new environment.
Before mapping events to your stream, Ascendon needs access credentials to connect with the Kinesis stream. The credentials were generated during stream creation, you can use them directly here.
.png?sv=2026-02-06&spr=https&st=2026-07-22T10%3A20%3A40Z&se=2026-07-22T10%3A32%3A40Z&sr=c&sp=r&sig=BJBVJw0bBr7aLROUjz1%2FJ4d%2B4bV0fUAbOqeIHinkY0s%3D)
Click on the Create New Value button and enter the following required values:
Name: Enter a descriptive name, typically matching your hub. This helps with identification and management. For Example - hub-west-dev, Ascendon-qa1
Region Endpoint: Paste the AWS region that was displayed when the stream was created. For Example - us-east-1
IAM Role ARN: Copy the IAM Role ARN from the Listener UI. This role defines the access permissions between Ascendon and your environment and click Save.
Event Notification Kinesis
Event Notification Kinesis refers to the process of sending real-time events notification from Ascendon to an AWS Kinesis stream. These notifications trigger based on configured actions (Event Notification Type) allowing the listener to receive and process the data instantly.
Search for Event Notification Kinesis using the search bar and select it. This will navigate you to the Event Notification Kinesis window. All pre-configured event notification are listed here
The credentials were generated during stream creation, you can use them directly here.
.png?sv=2026-02-06&spr=https&st=2026-07-22T10%3A20%3A40Z&se=2026-07-22T10%3A32%3A40Z&sr=c&sp=r&sig=BJBVJw0bBr7aLROUjz1%2FJ4d%2B4bV0fUAbOqeIHinkY0s%3D)
Click on the Create New Value button and enter the following required values:
Name: Provide a meaningful name for the event which we can co-relate with notification type. For Example - payment-received-prod.
Event Notification Type Code: Choose the relevant event type from the dropdown list. For Example - Order Submitted, Order Cancelled.
Event Context (optional): Add a short context note, such as customer segment, product type, or internal reference. This is useful for disambiguating similar events.
Stream Name: Paste the exact stream name copied from the ascendon listener stream.
AWS Credential ID: Choose the AWS Credential you configured earlier. This links Ascendon to your stream using valid permissions.
Click Save to save the configuration. Ascendon will now begin streaming event data to your graph.
Once an event notification is received and processed, the Ascendon Listener delivers the event payload in structured JSON format to the designated output within the graph.
The Kinesis stream, which powers Ascendon, retains data for 24 hours by default.
