AWS amazon-mq: Fix broken documentation links in IBM MQ migration guide
Summary
Corrected multiple URLs by removing extra double slashes to resolve broken links to Amazon MQ documentation.
Security assessment
The evidence shows a URL correction without altering security content. Broken links don't directly introduce vulnerabilities but hinder access to security documentation.
Evidence
+Gateway Queue Manager | A gateway Queue Manager is used to balance the workload. by routing traffic across multiple IBM MQ Queue Managers. | Network of Brokers | Amazon MQ provides [Network of Brokers](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/network-of-brokers) to route traffic to multiple brokers.
Diff
diff --git a/amazon-mq/latest/migration-guide/concept-chapter-ibm-amazon.md b/amazon-mq/latest/migration-guide/concept-chapter-ibm-amazon.md index 79074c9d9..90a5f1f64 100644 --- a//amazon-mq/latest/migration-guide/concept-chapter-ibm-amazon.md +++ b//amazon-mq/latest/migration-guide/concept-chapter-ibm-amazon.md @@ -21 +21 @@ Standard Queue Manager | Standard Queue Manager is similar to a broker but one -Gateway Queue Manager | A gateway Queue Manager is used to balance the workload. by routing traffic across multiple IBM MQ Queue Managers. | Network of Brokers | Amazon MQ provides [Network of Brokers](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/network-of-brokers) to route traffic to multiple brokers. +Gateway Queue Manager | A gateway Queue Manager is used to balance the workload. by routing traffic across multiple IBM MQ Queue Managers. | Network of Brokers | Amazon MQ provides [Network of Brokers](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/network-of-brokers) to route traffic to multiple brokers. @@ -23 +23 @@ Local Queues | A local queue is a definition of both a queue and the set of me -Remote Queues | Remote queues are used to refer to a queue which physically exists on a different IBM MQ Queue Manager, but connectivity is established using channels (Sender Channel and Receiver Channel) | Network of Brokers | This is achieved using a [Network of Brokers](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/network-of-brokers). Networks of Brokers connect to one another on a Network Connector. With a Netowork of Brokers, you can create connections across different Regions and Availability Zones. +Remote Queues | Remote queues are used to refer to a queue which physically exists on a different IBM MQ Queue Manager, but connectivity is established using channels (Sender Channel and Receiver Channel) | Network of Brokers | This is achieved using a [Network of Brokers](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/network-of-brokers). Networks of Brokers connect to one another on a Network Connector. With a Netowork of Brokers, you can create connections across different Regions and Availability Zones. @@ -31 +31 @@ Channel level Firewall | Channel level Firewall is used to blacklist/whitelist -Error Logs | Each IBM MQ Queue Manager has a configuration around transaction logs. It's similar to database logs. It has a size and policy (circular/linear). Any time there is a shared JMS transaction, the state is written in a log file for rollback or commit. | Amazon CloudWatch | CloudWatch logs are fully integrated with Amazon MQ. For more information, see [ Monitoring Amazon MQ Brokers Using Amazon CloudWatch](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/security-logging-monitoring-cloudwatch). +Error Logs | Each IBM MQ Queue Manager has a configuration around transaction logs. It's similar to database logs. It has a size and policy (circular/linear). Any time there is a shared JMS transaction, the state is written in a log file for rollback or commit. | Amazon CloudWatch | CloudWatch logs are fully integrated with Amazon MQ. For more information, see [ Monitoring Amazon MQ Brokers Using Amazon CloudWatch](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/security-logging-monitoring-cloudwatch). @@ -33 +33 @@ Listener | A listener is an IBM MQ process that listens for connections to the -LDAP Authentication | IBM MQ provides out of box connectivity to LDAP and group-based access to QM, queues, topics, etc. It also supports fine-grained access control at queue and topic levels. | IAM and LDAP Authentication | Simple authentication is available with Amazon MQ. Fine-grained access is only available at the broker user level. Fine-Grained Access Control at queue and topic level with access options to `Get`, `Put`. To learn more, see [ Messaging Authentication and Authorization](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/security-authentication-authorization). +LDAP Authentication | IBM MQ provides out of box connectivity to LDAP and group-based access to QM, queues, topics, etc. It also supports fine-grained access control at queue and topic levels. | IAM and LDAP Authentication | Simple authentication is available with Amazon MQ. Fine-grained access is only available at the broker user level. Fine-Grained Access Control at queue and topic level with access options to `Get`, `Put`. To learn more, see [ Messaging Authentication and Authorization](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/security-authentication-authorization).