You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
We have multiple S3 buckets for running Antivirus check. We are using the scan result posted to SNS to trigger corresponding event handlers. In our case each bucket is responsible for particular environment and sometimes it belongs to a separate application. So we thought of using filters in SNS. But to use that we have to send MessageAttributes as part of the message. Right now only the status and signature is sent as MessageAttributes. If bucket name is also included as a message attribute then we can filter that out at SNS level and it will be a lot cleaner.
This will involve adding bucket value here. Is it ok to send bucket information as a message attribute or is there any other way to handle this?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have multiple S3 buckets for running Antivirus check. We are using the scan result posted to SNS to trigger corresponding event handlers. In our case each bucket is responsible for particular environment and sometimes it belongs to a separate application. So we thought of using filters in SNS. But to use that we have to send MessageAttributes as part of the message. Right now only the
status
andsignature
is sent as MessageAttributes. If bucket name is also included as a message attribute then we can filter that out at SNS level and it will be a lot cleaner.This will involve adding bucket value here. Is it ok to send bucket information as a message attribute or is there any other way to handle this?
The text was updated successfully, but these errors were encountered: