@kenoir Question: (and I can merge this code without the question being answered) what happens if there is a catastrophic failure of the SQS service? By that I mean: if `@q.exists?` isn't true we'll try to create a new queue and assign it to `@q` and then we'll `sleep 1` until `@q` does exist. But if the SQS service has failed or we're not able to connect to it for whatever reason then we'll be `sleep`ing indefinitely and ultimately the process will never complete and surely we'll run out of memory or some such crash we'll occur.

Should we not be setting a time threshold (so: if it doesn't exist after 10 seconds then just raise an Error which we can store off or notifies the dev team so they know there was an issue -> as our application/service isn't publicly accessible we don't have to raise an error as the user just hits an endpoint and gets cached S3 data)