AWS EventBridge Event Trigger Subscription in Demo Tenant

Are Amazon EventBridge event trigger subscriptions supported in *.identitynow-demo.com (AKA Demohub) tenants?

When trying to create one through the UI, the following error occurs:
image

The same error occurs when trying to create the subscription via the event trigger subscription and SP-Config APIs.

Hi Nathan, I wanted to make sure I understood how you tried to create this in the UI. Did you navigate to Event Triggers menu within the UI? Normally, this is where you should have a list of pre-defined available triggers you can subscribe to. I’ve not seen Amazon Event hub in those available triggers. I could see ISC receiving an Amazon Event Hub event, but I would use SaaS Workflows for that.

I saw no one responded to this and wanted to follow up with you, because some clarification might help get this answered.

Hey William, thanks for responding!

This post is regarding the Amazon EventBridge subscription method for the Event Trigger Service:

This method sits alongside HTTP and native Workflows integrations with the Event Trigger Service. Neil McGlennon provides a great overview of this feature here:

1 Like

@nsorlien - This should work regardless of tenant type. If not, that’s a bug, and I would raise that with SailPoint. :slight_smile:

Good to know, thanks!

@colin_mckibben Is this something you could pass along to the right team in SailPoint? We opened a regular support ticket a while back but were told SailPoint Support cannot assist with demo tenants.

Did you verify that the same AWS ID will work in your sandbox or prod tenants?

Yep, I just tested the value in a customer’s sandbox tenant and it still works there. We have seen this issue across the 4 different demo tenants we’ve had access to over the last year or so.

What’s your case number? I can review the details.

The case was CS0244863

Edit: CS0245305 as well

I have opened a ticket (TSTRM-8602) for our DemoHub team to look into this. I’ll keep you updated when there is a resolution.

1 Like

@colin_mckibben Any updates on this one? Just checking in before the topic automatically closes :slight_smile:

I just asked support where they are on this.

The original demohub tenant you provided in your support case is no longer active. Do you have a different demohub instance that is having the same issue?

Yep, I will DM you the URL.

This is looking like a bug, and has been raised to engineering. Ticket number is TSTRM-8602.

@colin_mckibben Checking in before the topic closes again, can you see if there are any updates on the internal ticket?

Hi Nathan,
It looks like there was an update recently. I will tag @developer_advocates to see if they can help while Colin is out.

Nathan, here is what engineering has to say about your issue:

AWS account ID is not correct or not presented correctly.

Is this the same account ID that you are using in your production tenant? Is it a different one?

I just tested the value in a customer’s sandbox tenant and it still works there. We have seen this issue across the 4 different demo tenants we’ve had access to over the last year or so. Do they need an account ID to test with?

yes. Please send me a private message with the AWS account ID so I can pass that to engineering.