[SERVER-51817] Setting up a Trigger with AWS Eventbridge does not work Created: 23/Oct/20  Updated: 06/Dec/22  Resolved: 26/Oct/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Robbert-Jan van der Dennen Assignee: Backlog - Triage Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Triage
Operating System: ALL
Steps To Reproduce:

trying the steps documented in https://docs.atlas.mongodb.com/triggers/eventbridge/ 

Participants:

 Description   

Setting up a Trigger with AWS Eventbridge does not work. After trying the steps documented in https://docs.atlas.mongodb.com/triggers/eventbridge/ it does not work. Although the trigger thinks that the event was sent to the AWS eventbridge, it never arrives.
It also isn't possible to define any required access permissions for other accounts and organizations and then click Associate.
If you do try to do so, the following error is displayed:
Invalid policy: 1 validation error detected: Value 'aws.partner/mongodb.com/stitch.trigger/1a2b3d6ac922dca098455570' at 'eventBusName' failed to satisfy constraint: Member must satisfy regular expression pattern: [\.\-_A-Za-z0-9]+



 Comments   
Comment by Robbert-Jan van der Dennen [ 26/Oct/20 ]

Hi Edwin Zhou,

 

Thanks for the suggestion, but I was already denied support when I tried that.

I was hoping to be more succesful here.

 

Kind regards,

Robbert-Jan van der Dennen

Comment by Edwin Zhou [ 26/Oct/20 ]

Hi robbert-jan.van.der.dennen@zelfstroom.nl,

The SERVER project is for bugs and feature suggestions for the MongoDB server. To inform our Atlas team of issues you are having or feature requests you'd like to suggest, please reach out to the Atlas support team via Intercom. You can do this by clicking the round green button at the bottom right of the cluster view page in Atlas.

Best,

Edwin

Generated at Thu Feb 08 05:26:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.