Unable to accept new SNS subscriptions

[mcalfin]

Now tracked in https://mattermost.atlassian.net/browse/MM-19289

We currently have Mattermost 5.13.0 running and recently tried to add this plugin. However, anytime we try to confirm a subscription we get the following error:

SNS BOT Error: We could not decode the action

The notification of a new subscription comes through successfully and provides a clickable button to confirm the subscription, but fails to actually subscribe. We've tried using different channels as well as confirming different subscriptions If I can be of any help and provide any kind of logs, please let me know. We'd really like to use this plugin to have our cloudwatch alarms trigger a mattermost alert.

[hanzei]

@cpoile Can you help with this issue?

[cpanato]

I would like to see the config for the plugin, and the logs if possible @mcalfin

/cc @jfrerich @levb

[levb]

@mcalfin Would it be possible for you to provide the logs as requested above? Otherwise we'll need to close this ticket as "Not reproduced" for now.

[levb]

Not reproduced.

[aberenyi]

Sorry to necrobump this, but I'm facing the exact same problem.

Interestingly there is nothing in mattermost.log that relates to this issue...

/cc @cpanato @levb @hanzei

[levb]

There's also a #28. Clearly there's an issue. @jfrerich Can you please instrument the AWS client to dump the payload in the log when decoding failures happen?

[mcalfin]

Sorry I disappeared. This is definitely still an issue with the latest mattermost 5.21 but we worked around it and moved on since we've been extremely busy. I edited the source to the aws plugin and had it dump the subscribe URL and subscribed to it manually. Nothing was showing up in the logs regarding the errors trying to accept the subscription and the configuration is pretty standard. Once subscribed everything seems to be working as normal.

If any additional info is needed from me let me know. I'd be happy to go back and revisit this.

[theomegabit]

So i am not certain if this is related to this exact issue but I am unable to fully complete the setup from AWS. Sending the subscription to my URL w/ my token is simply not resulting in anything being posted in the channel. Log entry isn't too terribly helpful either

{"level":"error","ts":1588796126.387565,"caller":"mlog/log.go:175","msg":"Invalid or missing channel_id parameter in request URL.","path":"/api/v4/channels/posts","request_id":"geogy8349pgqbr7fxut97ce1xy","ip_addr":"<IP>","user_id":"<user_ID>","method":"GET","err_where":"Context","http_code":400,"err_details":""}

It's complaining about the team/channel name but it is entered in the correct <teamName,channel-name-with-dash> that it requires. My user is a system admin and i created this private channel (does that matter?) in question.

I tried putting a non-existent channel to have it create its own but that did not work as well.