Why it is good design practice to send AWS S3 object notifications to SNS instead of to SQS or Lambda ?

Amazon Simple Storage Service (Amazon S3) is a cost-efficient and highly scalable persistent or temporary object storage that most of the organizations consider using to store regular or big data.

Before Nov 2014, whenever objects were created/deleted/e.t.c there was no notification system to transmit the events. To detect those events we need to either have every process that uploaded to S3 subsequently trigger back end code in some way or poll the S3 bucket to see if objects had been added/deleted e.t.c. This adds additional coupling to the system.

Once S3 event notification introduced in Nov 2014, whenever S3 generate object creation/deletion/restore/RRS/ e.t.c events, we can configure to notify services like SNS or SQS or LAMBDA

At any point, an event(like object creation or deletion e.t.c) can be configured to send a notification to either SNS or SQS, or Lambda as shown below.

So which notification destination to choose→