AWS amazon-mq: Fix broken documentation links
Summary
Corrected invalid URLs by removing double slashes in Amazon MQ architecture guide links
Security assessment
Change fixes broken documentation links without altering security content
Evidence
-Amazon MQ provides a variety of broker configurations, various instance sizes for different workloads, and broker options such as single instance, single instance mesh, active/standby instance or active/standby mesh for high availabilty and message durability. To learn more about supported broker options, see [Amazon MQ Broker Architecture](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/amazon-mq-broker-architecture).
Diff
diff --git a/amazon-mq/latest/migration-guide/tibco-amazon-mq-architecture.md b/amazon-mq/latest/migration-guide/tibco-amazon-mq-architecture.md index 7db22b71a..46390d6f5 100644 --- a//amazon-mq/latest/migration-guide/tibco-amazon-mq-architecture.md +++ b//amazon-mq/latest/migration-guide/tibco-amazon-mq-architecture.md @@ -9 +9 @@ -Amazon MQ provides a variety of broker configurations, various instance sizes for different workloads, and broker options such as single instance, single instance mesh, active/standby instance or active/standby mesh for high availabilty and message durability. To learn more about supported broker options, see [Amazon MQ Broker Architecture](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/amazon-mq-broker-architecture). +Amazon MQ provides a variety of broker configurations, various instance sizes for different workloads, and broker options such as single instance, single instance mesh, active/standby instance or active/standby mesh for high availabilty and message durability. To learn more about supported broker options, see [Amazon MQ Broker Architecture](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-broker-architecture). @@ -27 +27 @@ For _App 1_ to communicate with _App 2_ : - 3. Queues and users can be created and managed in the AWS Console. To learn more, see [Amazon MQ Basic Elements](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/amazon-mq-basic-elements). + 3. Queues and users can be created and managed in the AWS Console. To learn more, see [Amazon MQ Basic Elements](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-basic-elements). @@ -34 +34 @@ For _App 1_ to communicate with _App 2_ : - * A _Global Topic_ with the same name has to be created on other EMS Servers for forwarding messages to the Topic on those EMS Servers. In Amazon MQ, a _global topic_ is not required. Once 2 brokers are connected using a [network connector](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/child-element-details.html#networkConnector), they begin to share all queues/topics, and their data. + * A _Global Topic_ with the same name has to be created on other EMS Servers for forwarding messages to the Topic on those EMS Servers. In Amazon MQ, a _global topic_ is not required. Once 2 brokers are connected using a [network connector](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/child-element-details.html#networkConnector), they begin to share all queues/topics, and their data. @@ -41 +41 @@ For _App 1_ to communicate with _App 2_ : - * A network bridge from a topic to a queue can be used in TIBCO EMS architecture to avoid the naming issue with routed queues and to provide multi-hop capability between EMS servers using a Topic. In Amazon MQ, queue names are consistent and all topic/queue messages are shared among a [Networks of Brokers](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/network-of-brokers). + * A network bridge from a topic to a queue can be used in TIBCO EMS architecture to avoid the naming issue with routed queues and to provide multi-hop capability between EMS servers using a Topic. In Amazon MQ, queue names are consistent and all topic/queue messages are shared among a [Networks of Brokers](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/network-of-brokers).