AWS amazonq documentation change
Summary
Updated trusted access reference to profile sharing, removed account limit note, and added managed application creation limit
Security assessment
Changes involve documentation link updates and operational limits clarification without security-specific content or vulnerability addressing.
Diff
diff --git a/amazonq/latest/qdeveloper-ug/subscribe-management.md b/amazonq/latest/qdeveloper-ug/subscribe-management.md index 29224676a..9dbb3acfc 100644 --- a/amazonq/latest/qdeveloper-ug/subscribe-management.md +++ b/amazonq/latest/qdeveloper-ug/subscribe-management.md @@ -30,4 +29,0 @@ Before you begin, make sure that: -###### Note - -You can enable Amazon Q Developer Pro in a maximum of 50 AWS accounts within an organization. - @@ -56 +52 @@ The **Create Amazon Q Developer Pro application** dialog box may appear. It only - 5. Review the contents of the dialog box. For help with the **Share Amazon Q Developer settings with member account** check box, see [Enabling trusted access in Amazon Q Developer](./q-admin-trusted-access.html). + 5. Review the contents of the dialog box. For help with the **Share Amazon Q Developer settings with member account** check box, see [Enabling profile sharing in Amazon Q Developer](./q-admin-profile-sharing.html). @@ -87 +83 @@ If you don't enable identity-aware console sessions, users can still use Amazon -When you subscribed existing users in your management account, Amazon Q created the following resources on your behalf: +When you subscribed users in your management account, Amazon Q created the following resources on your behalf: @@ -92,0 +89,4 @@ When you subscribed existing users in your management account, Amazon Q created +###### Note + +Amazon Q can create the **QDefaultProfile** managed application in a maximum of 50 AWS accounts within an organization. +