Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to get notification from event bus ARN #29

Open
adnanmansuri44 opened this issue Feb 9, 2022 · 5 comments
Open

How to get notification from event bus ARN #29

adnanmansuri44 opened this issue Feb 9, 2022 · 5 comments

Comments

@adnanmansuri44
Copy link

HI,
We want this notification in the email, where the only option to get it via SES or event bus ARN then SNS. SES required email verification and exchange policy to be allowed for delivery which is difficult

We want to explore event bus option. after the event is received on the event bus it should trigger to SNS, SQS or any other service which required event pattern to be created. What will be event pattern sample or parameter to get that all events to SNS or SQS from event bus? and it should be in json format. So is lambda sending events into json format?

Please assist

Adnan

@gmridula
Copy link
Contributor

Thank you Adnan for your feedback. We are currently making changes on how the health events get pushed to eventbus. ETA for the beta release is two weeks from now. Stay tuned and we will keep you posted.

@vaquarkhan
Copy link

is above request completed ?

@adnanmansuri44
Copy link
Author

I didnt get chance to check updates. need to implement and test event bus format.

@vaquarkhan
Copy link

It just required boto3 call and ask sns arn in loud formation

@adnanmansuri44
Copy link
Author

i check latest cloud formation template. unable to find the parameter for sns arn. target is only till event bus arn. from bus to other services how to fetch it? @vaquarkhan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants