Add 'standard' SQS endpoint strategy (#877)

content/en/user-guide/aws/sqs/index.md

@@ -169,6 +169,7 @@ You can control the format of the generated Queue URLs by setting the environmen
 
 | Value    | URL format                                                                 | Description                                                                                                                                                                                                                                                         |
 | -------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `standard` | `sqs.<region>.localhost.localstack.cloud:4566/<account_id>/<queue_name>` | This strategy resembles AWS the closest, see [Identifiers for Amazon SQS](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-message-identifiers.html#sqs-general-identifiers), and comes with full multi-account and multi-region support. |
 | `domain` | `<region>.queue.localhost.localstack.cloud:4566/<account_id>/<queue_name>` | This strategy behaves like the [SQS legacy service endpoints](https://docs.aws.amazon.com/general/latest/gr/sqs-service.html#sqs_region), and uses `localhost.localstack.cloud` to resolve to localhost. While using the `us-east-1` region, the `<region>.` prefix is omitted. |
 | `path`   | `localhost:4566/queue/<region>/<account_id>/<queue_name>`                  | An alternative that can be useful if you cannot resolve LocalStack's `localhost` domain.                                                                                                                                                                               |
 | `off`    | `localhost:4566/<account_id>/<queue_name>`                                 | It is the current default for maintaining backward compatibility. However, this format does not encode the region information. As a result, you will encounter limitations when querying queues with the same name that exist in different regions.                                                                               |