AWS amazon-mq documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in hybrid architecture section
Security assessment
Branding update without security implications. No changes to security recommendations.
Diff
diff --git a/amazon-mq/latest/migration-guide/concept-chapter-about.md b/amazon-mq/latest/migration-guide/concept-chapter-about.md index 5f5384ab8..588e510f9 100644 --- a//amazon-mq/latest/migration-guide/concept-chapter-about.md +++ b//amazon-mq/latest/migration-guide/concept-chapter-about.md @@ -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 [AWS 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 [AWS VPN](https://aws.amazon.com/vpn/) or [Direct Connect](https://aws.amazon.com/directconnect/).