AWS EventBridge Event Trigger Subscription in Demo Tenant

[colin_mckibben]

I was able to reproduce this issue with a fresh demohub tenant. I can use your AWS account ID when subscribing to a trigger on a production tenant, but I get the same error message as you when doing the same for a demohub tenant. I will pass this along to engineering.

[colin_mckibben]

It turns out that you will need to open an AWS support case to whitelist the partner namespace aws.partner/sailpoint.com.test for each AWS account ID you plan on using with identitynow-demo.com tenants. This is not something that SailPoint can fulfill for you. You must submit the support case to AWS. Because your AWS account ID is not whitelisted for the partner namespace, your demo tenants do not recognize the account ID, hence the error message you are getting.

Please try this out and let us know if whitelisting that namespace works in your case.

[nsorlien (Nathan Sorlien)]

Interesting! I’ll look into opening a ticket with AWS.

In the meantime, I noticed your devrel tenant has a unique prefix under the main SailPoint partner namespace:

Could SailPoint do something similar with demo tenants as opposed to using the test namespace?

[nsorlien (Nathan Sorlien)]

AWS support was able to whitelist the aws.partner/sailpoint.com.test namespace in our AWS account and we can now integrate with Amazon EventBridge in our partner DemoHub tenant!