To expand on this, this is very valuable when creating serverless applications via serverless.yml or any kind of "Infrastructure as Code" tool.

Here is an example where we can very simply put the queue URL returned by SQS into an environment variable:

provider:
    ...
    environment:
        APP_ENV: prod
        SQS_URL:
            Ref: AlertQueue

resources:
    Resources:
        AlertQueue:
            Type: AWS::SQS::Queue

Without that feature, we would have to transform the queue URL to match Symfony's prefix (sqs://), which is hard to do here.

Solving that issue would allow to merge Bref's Symfony Messenger bridge with the official SQS driver.

FYI SQS URLs are distinguishable via a prefix, this is what is done in Bref:

https://github.com/brefphp/symfony-messenger/blob/3ee64570ba6b5693052e4e8eb601ee8d2765392a/src/Service/Sqs/SqsTransportFactory.php#L29

    public function supports(string $dsn, array $options): bool
    {
        return preg_match('#^https://sqs\.[\w\-]+\.amazonaws\.com/.+#', $dsn) === 1;
    }

Can I bring another perspective here...

If I was allowed to tag a service as a Transport.. Then would I be able to initialize my SqsService with the plain URL?

AFAIK I can't tag services as transports and avoid factories.. Allowing the above, I could declare my own Connection with the simple URL and pass it to my own Transport..

Then I could use it into routing..

awesome thanks @starred-gijs!