Our AWS environment is setup to differentiate the Sandbox and production environments
based on different VPC Setup, so, the VPC for the sandbox cannot talk to the VPC (s) used
They only have a single AWS Account ID, which has no way to differentiate the SB from
production environments. The setup of the EventBus event triggers in SailPoint only has
the AWS Account ID.
Has anyone else have this situation where 2 environments use the same AWS account, and how
have you solved it?
My thought is that once the EventBus is associated with the proper environment(SB or Prod)
when it’s initially setup, that should lock it to the environment. Can anyone see any issue with this?