Do I need SQS queues to store remote data in the Amazon Web Services (AWS) cloud?
No SQS is not required. SQS is a publicly available service that only requires an authentication token in the request header.  You can grant that using an IAM user account with security keys or if the calling service is another AWS account you can grant access by IAM roles.  S3 is also a public service that works similar to SQS with regards to access. The process for setting up cross AWS account access is a bit different but the concept is the same.  You also can send data directly to an EC2 instance by either assigning it a public IP address in a public subnet or by using an Elastic Load Balancer (ELB). 

SQS is a queue service that only holds onto the data for another service to pull down. However if you are looking to have a service broadcast a dataset to multiple destinations you are looking for SNS. SNS will allow you to send to multiple destinations and each destination can have its own type of delivery. For example if you posted a message to SNS you could have it deliver that message to a lambda function in AWS and a web endpoint that accepts JSON. 

The only caveat to all of this is that SNS takes the message it receives and sends it on to the destinations without any transformation so each destination will receive the exact same message and be responsible for extracting the data.