Is your feature request related to a problem? Please describe.
SNS endpoint subscriptions must expose a public facing HTTP server ( unless I missed something ) and therefore make it possible for untrusted sources to post messages to the event bus as long as the message comply with basic message format.

Describe the solution you'd like
The SNS source should verify the signature of the

Brief summary of issue / Description of requested feature:

See:

Steps to reproduce the issue / Reasons for adding feature:

1. Open up alias editor on macOS.

Error output / Expected result of feature

Fonts should be consistent & professional.

Extra infor

In the docs -- https://github.com/tektoncd/triggers/blob/master/docs/eventlisteners.md#serviceaccountname -- it states that ServiceAccountName is required. In our environment an EventListener author would never know what ServiceAccounts are available so we would like to use "default" in this case or better still follow Tekton Pipelines logic -- https://github.com/tektoncd/pipeline/blob/db66eca6112

Task:

• Update invokefunction to return the response headers
• Update the caller function named Invoke to return the body, statusCode and errors
• Update example to print statusCode and body

Suggested by Simon Pezcler and Rishabh Gupta so that connectors can do better debug and potentially use the result for something.

Right now the result is abandoned.

especially in slack command, we use table Scans a lot
might need DB structure switching a little to give a better ID and perhaps GSI