I'm really failing to see how that's any clearer. If you're looking at SQS you probably already know it's an AWS service, and pubsub seems less descriptive than queue...
pubsub would also be misleading, given SQS does not support the pub/sub pattern. It's a queue where each message is processed once by a single consumer; it's not a pub/sub system where multiple consumers can subscribe to messages of interest.