This isn't on anyone's radar for something planned.
However, you could try to implement it. Since SQS doesn't support pub/sub you'd likely need to use SNS as well for the pub/sub portions of the transport - or implement something like MassTransit.RuntimeServices to manage that. It's non-trivial to build, but there are a number of transport examples if you were interested in doing so. I would, given that I was working on AWS, just spin up a RabbitMQ cluster and use that. I/O will kinda suck if you hit high volumes but SQS will start getting pretty expensive then anyways, so more hardware will make sense.