AWS amazon-mq documentation change
Summary
Updated documentation links by adding double slashes in URLs and fixed a typo ('interlopability' to 'interoperability')
Security assessment
The changes primarily correct URL formatting and fix a typo. There is no mention of security vulnerabilities, patches, or new security features. The security-related sections (TLS usage, VPC access, encryption) only have updated URLs but no substantive content changes.
Diff
diff --git a/amazon-mq/latest/migration-guide/concept-chapter-about.md b/amazon-mq/latest/migration-guide/concept-chapter-about.md index 588e510f9..519961e3d 100644 --- a//amazon-mq/latest/migration-guide/concept-chapter-about.md +++ b//amazon-mq/latest/migration-guide/concept-chapter-about.md @@ -34 +34 @@ You can connect your broker to Amazon MQ without any code changes if you current -For more information about connecting to an Amazon MQ managed broker, see [Working Examples of Using Java Message Service (JMS) with ActiveMQ](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-working-java-example) in the _Amazon MQ Developer Guide_. +For more information about connecting to an Amazon MQ managed broker, see [Working Examples of Using Java Message Service (JMS) with ActiveMQ](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/amazon-mq-working-java-example) in the _Amazon MQ Developer Guide_. @@ -38 +38 @@ For more information about connecting to an Amazon MQ managed broker, see [Worki -To replicate _persistence mode_ or _sync point control_ options with Amazon MQ, you can deploy your brokers as [active/standby brokers](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/active-standby-broker-deployment). In the active/standby deployment, brokers use shared storage across multiple Availability Zones, with an optional time to live (TTL). +To replicate _persistence mode_ or _sync point control_ options with Amazon MQ, you can deploy your brokers as [active/standby brokers](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/active-standby-broker-deployment). In the active/standby deployment, brokers use shared storage across multiple Availability Zones, with an optional time to live (TTL). @@ -44 +44 @@ For more information about how Amazon MQ ensures message durability, see Availab -Depending on the interlopability of your applications and the type of access that they need, you can permit public access, [VPN access](https://docs.aws.amazon.com/vpn/latest/s2svpn/VPC_VPN), or [VPC access](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc) using Amazon Virtual Private Cloud (Amazon VPC). +Depending on the interlopability of your applications and the type of access that they need, you can permit public access, [VPN access](https://docs.aws.amazon.com//vpn/latest/s2svpn/VPC_VPN), or [VPC access](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc) using Amazon Virtual Private Cloud (Amazon VPC). @@ -46 +46 @@ Depending on the interlopability of your applications and the type of access tha -In a _hybrid architecture_ where on-premises systems need access to resources in the cloud, we recommend setting up your Amazon MQ managed brokers with _public network access_. You can also achieve a hybrid solution by using [AWS VPN](https://aws.amazon.com/vpn/) or [Direct Connect](https://aws.amazon.com/directconnect/). +In a _hybrid architecture_ where on-premises systems need access to resources in the cloud, we recommend setting up your Amazon MQ managed brokers with _public network access_. You can also achieve a hybrid solution by using [Site-to-Site VPN](https://aws.amazon.com//vpn/) or [Direct Connect](https://aws.amazon.com//directconnect/). @@ -50 +50 @@ In a _hybrid architecture_ where on-premises systems need access to resources in -If your resources are primarily deployed within the AWS Cloud, we recommend configuring your Amazon MQ brokers with Amazon VPC. For network access across multiple VPCs, you can use [VPC peering](https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html). +If your resources are primarily deployed within the AWS Cloud, we recommend configuring your Amazon MQ brokers with Amazon VPC. For network access across multiple VPCs, you can use [VPC peering](https://docs.aws.amazon.com//vpc/latest/peering/what-is-vpc-peering.html). @@ -54 +54 @@ If your resources are primarily deployed within the AWS Cloud, we recommend conf -Amazon MQ supports durability-optimized brokers backed by [Amazon Elastic File System (Amazon EFS)](https://aws.amazon.com/efs/). You can configure [single-instance brokers](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/single-broker-deployment) (one broker in one Availability Zone) or [active/standby brokers](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/active-standby-broker-deployment) (two brokers in two different Availability Zones). In either configuration, Amazon MQ can automatically provision infrastructure for high message durability by storing messages redundantly across multiple Availability Zones. +Amazon MQ supports durability-optimized brokers backed by [Amazon Elastic File System (Amazon EFS)](https://aws.amazon.com//efs/). You can configure [single-instance brokers](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/single-broker-deployment) (one broker in one Availability Zone) or [active/standby brokers](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/active-standby-broker-deployment) (two brokers in two different Availability Zones). In either configuration, Amazon MQ can automatically provision infrastructure for high message durability by storing messages redundantly across multiple Availability Zones. @@ -60 +60 @@ In the event of a broker or Availability Zone failure, active/standby brokers au -To achieve high availability and message durability, you can use a [network of brokers](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/network-of-brokers.html). A network of brokers is a series of simultaneously active single-instance or active/standby brokers that allows you to rapidly scale your throughput and connection count. You can configure a network of brokers in a variety of topologies depending on your application's needs. +To achieve high availability and message durability, you can use a [network of brokers](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/network-of-brokers.html). A network of brokers is a series of simultaneously active single-instance or active/standby brokers that allows you to rapidly scale your throughput and connection count. You can configure a network of brokers in a variety of topologies depending on your application's needs. @@ -79 +79 @@ Amazon MQ offers the following topology options to support a variety of messagin -For more information about using Amazon MQ to set up the right broker topology for your cloud architecture, see [ Amazon MQ Broker Architecture](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-broker-architecture) in the _Amazon MQ Developer Guide_. +For more information about using Amazon MQ to set up the right broker topology for your cloud architecture, see [ Amazon MQ Broker Architecture](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/amazon-mq-broker-architecture) in the _Amazon MQ Developer Guide_. @@ -83 +83 @@ For more information about using Amazon MQ to set up the right broker topology f -Revising a broker configuration or an ActiveMQ user does not immediately apply those changes. For your changes to take effect, you must wait for the next maintenance window or reboot the broker. For more information, see [Amazon MQ Broker Configuration Lifecycle](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-broker-configuration-lifecycle) in the _Amazon MQ Developer Guide_. +Revising a broker configuration or an ActiveMQ user does not immediately apply those changes. For your changes to take effect, you must wait for the next maintenance window or reboot the broker. For more information, see [Amazon MQ Broker Configuration Lifecycle](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/amazon-mq-broker-configuration-lifecycle) in the _Amazon MQ Developer Guide_. @@ -89 +89 @@ With Amazon MQ you can scale your messaging middleware horizontally, vertically, -_Horizontal scaling_ enables you to increase your throughput and connection count without interruptions, because your resources remain active and online. To scale horizontally, you can deploy a [network of brokers](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/network-of-brokers.html) in an active/standby configuration across multiple Availability Zones. +_Horizontal scaling_ enables you to increase your throughput and connection count without interruptions, because your resources remain active and online. To scale horizontally, you can deploy a [network of brokers](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/network-of-brokers.html) in an active/standby configuration across multiple Availability Zones. @@ -91 +91 @@ _Horizontal scaling_ enables you to increase your throughput and connection coun -To scale your resources _vertically_ , you can increase the compute capacity of your broker instances from `mq.t2.micro` (1 vCPU and 1 GiB) up to `mq.m5.4xlarge` (16 vCPU and 64 GiB). For more information about Amazon MQ instance types, see [Instance Types](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/broker#broker-instance-types) in the _Amazon MQ Developer Guide_. +To scale your resources _vertically_ , you can increase the compute capacity of your broker instances from `mq.t2.micro` (1 vCPU and 1 GiB) up to `mq.m5.4xlarge` (16 vCPU and 64 GiB). For more information about Amazon MQ instance types, see [Instance Types](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/broker#broker-instance-types) in the _Amazon MQ Developer Guide_. @@ -97 +97 @@ Choosing larger broker instance types might not improve overall system throughpu -Amazon MQ also supports creating throughput-optimized message brokers backed by [Amazon Elastic Block Store (Amazon EBS)](https://aws.amazon.com/ebs/). These brokers are ideal for applications such as high-volume order processing, stock trading, and text processing. +Amazon MQ also supports creating throughput-optimized message brokers backed by [Amazon Elastic Block Store (Amazon EBS)](https://aws.amazon.com//ebs/). These brokers are ideal for applications such as high-volume order processing, stock trading, and text processing. @@ -134 +134 @@ Performance numbers can vary depending on multiple configuration parameters. For -You can measure the throughput of your Amazon MQ brokers using [JMS Benchmark](https://aws.amazon.com/blogs/compute/measuring-the-throughput-for-amazon-mq-using-the-jms-benchmark/). +You can measure the throughput of your Amazon MQ brokers using [JMS Benchmark](https://aws.amazon.com/blogs//compute/measuring-the-throughput-for-amazon-mq-using-the-jms-benchmark/). @@ -140 +140 @@ You can set up your Amazon MQ brokers for low-latency messaging, with latency of -Using _in-memory_ storage can further reduce overall latency across your messaging architecture. For more information on how different storage types can affect latency, see [Differences Between Storage Types](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/broker-storage#differences-between-storage-types) in the _Amazon MQ Developer Guide_. +Using _in-memory_ storage can further reduce overall latency across your messaging architecture. For more information on how different storage types can affect latency, see [Differences Between Storage Types](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/broker-storage#differences-between-storage-types) in the _Amazon MQ Developer Guide_. @@ -154 +154 @@ You can optimize and fine-tune the performance of your topics. For more informat -With Amazon MQ you control who is allowed to create or modify brokers, and which applications are allowed to send and receive messages. For more information about authentication options, and how to integrate the [Lightweight Directory Access Protocol (LDAP)](https://ldap.com/) with your Amazon MQ brokers, see [Messaging Authentication and Authorization for ActiveMQ](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/security-authentication-authorization) in the _Amazon MQ Developer Guide_. +With Amazon MQ you control who is allowed to create or modify brokers, and which applications are allowed to send and receive messages. For more information about authentication options, and how to integrate the [Lightweight Directory Access Protocol (LDAP)](https://ldap.com/) with your Amazon MQ brokers, see [Messaging Authentication and Authorization for ActiveMQ](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/security-authentication-authorization) in the _Amazon MQ Developer Guide_. @@ -156 +156 @@ With Amazon MQ you control who is allowed to create or modify brokers, and which -Connections to Amazon MQ brokers use Transport Layer Security (TLS). To isolate your brokers in a private virtual network, you can restrict access to a private endpoint within a VPC. To control network access to your brokers, you can configure security groups in the VPC. For more information, see [Security Best Practices for Amazon MQ](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/using-amazon-mq-securely) in the _Amazon MQ Developer Guide_. +Connections to Amazon MQ brokers use Transport Layer Security (TLS). To isolate your brokers in a private virtual network, you can restrict access to a private endpoint within a VPC. To control network access to your brokers, you can configure security groups in the VPC. For more information, see [Security Best Practices for Amazon MQ](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/using-amazon-mq-securely) in the _Amazon MQ Developer Guide_. @@ -158 +158 @@ Connections to Amazon MQ brokers use Transport Layer Security (TLS). To isolate -Amazon MQ encrypts messages at rest and in transit using encryption keys that it manages and stores securely in [AWS Key Management Service (AWS KMS)](https://aws.amazon.com/kms/). AWS KMS helps reduce the operational burden and complexity involved in protecting sensitive data. With encryption at rest, you can build security-sensitive applications that meet encryption compliance and regulatory requirements. +Amazon MQ encrypts messages at rest and in transit using encryption keys that it manages and stores securely in [AWS Key Management Service (AWS KMS)](https://aws.amazon.com//kms/). AWS KMS helps reduce the operational burden and complexity involved in protecting sensitive data. With encryption at rest, you can build security-sensitive applications that meet encryption compliance and regulatory requirements. @@ -162 +162 @@ Amazon MQ encrypts messages at rest and in transit using encryption keys that it -For additional security, we highly recommend designing your application to use [client-side encryption](https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/introduction). +For additional security, we highly recommend designing your application to use [client-side encryption](https://docs.aws.amazon.com//encryption-sdk/latest/developer-guide/introduction). @@ -164 +164 @@ For additional security, we highly recommend designing your application to use [ -For more information about Amazon MQ security and how messaging data is encrypted, see [Data Protection in Amazon MQ](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/data-protection) in the _Amazon MQ Developer Guide_. +For more information about Amazon MQ security and how messaging data is encrypted, see [Data Protection in Amazon MQ](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/data-protection) in the _Amazon MQ Developer Guide_. @@ -168 +168 @@ For more information about Amazon MQ security and how messaging data is encrypte -By default, each Amazon MQ broker can support 1,000 connections (or 100 connections for `mq.t2.micro` brokers). To allow multiple consumers to share connections to your Amazon MQ brokers and to improve overall performance, we recommend using _pooled connections_. For more information, see [Always Use Connection Pooling](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/connecting-to-amazon-mq.html#always-use-connection-pooling) in the _Amazon MQ Developer Guide_. +By default, each Amazon MQ broker can support 1,000 connections (or 100 connections for `mq.t2.micro` brokers). To allow multiple consumers to share connections to your Amazon MQ brokers and to improve overall performance, we recommend using _pooled connections_. For more information, see [Always Use Connection Pooling](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/connecting-to-amazon-mq.html#always-use-connection-pooling) in the _Amazon MQ Developer Guide_. @@ -170 +170 @@ By default, each Amazon MQ broker can support 1,000 connections (or 100 connecti -You can request an increase for many [broker usage quotas](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-limits.html#broker-limits) for your AWS account. For more information, see [AWS service quotas](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) in the _AWS General Reference_. +You can request an increase for many [broker usage quotas](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/amazon-mq-limits.html#broker-limits) for your AWS account. For more information, see [AWS service quotas](https://docs.aws.amazon.com//general/latest/gr/aws_service_limits.html) in the _AWS General Reference_. @@ -178 +178 @@ Amazon MQ brokers can also support more complex messaging patterns such as compo -For more information, see [Amazon MQ Broker Configuration Parameters](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-broker-configuration-parameters) in the _Amazon MQ Developer Guide_. +For more information, see [Amazon MQ Broker Configuration Parameters](https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/amazon-mq-broker-configuration-parameters) in the _Amazon MQ Developer Guide_. @@ -188 +188 @@ For data transferred in and out of Amazon MQ, you pay standard AWS data transfer -To get started, Amazon MQ offers a Free Tier, which includes up to 750 hours of a single-instance `mq.t2.micro` or `mq.t3.micro` broker per month, and up to 5 GB of durability-optimized storage per month for one year. For more information on the Free Tier, pricing, and associated costs, see [Amazon MQ Pricing](https://aws.amazon.com/amazon-mq/pricing/). +To get started, Amazon MQ offers a Free Tier, which includes up to 750 hours of a single-instance `mq.t2.micro` or `mq.t3.micro` broker per month, and up to 5 GB of durability-optimized storage per month for one year. For more information on the Free Tier, pricing, and associated costs, see [Amazon MQ Pricing](https://aws.amazon.com//amazon-mq/pricing/).