AWS amazonq documentation change
Summary
Updated documentation about account limits and resource creation. Moved the 50-account limit note to context about the QDefaultProfile managed application.
Security assessment
The changes clarify usage limits and resource ownership but do not address security vulnerabilities or describe security features. The 50-account limit appears to be a service quota rather than a security control.
Diff
diff --git a/amazonq/latest/qdeveloper-ug/subscribe-member.md b/amazonq/latest/qdeveloper-ug/subscribe-member.md index e098a3afb..d20b0af2d 100644 --- a/amazonq/latest/qdeveloper-ug/subscribe-member.md +++ b/amazonq/latest/qdeveloper-ug/subscribe-member.md @@ -39,4 +38,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. - @@ -135 +131 @@ If you're using organization instance, contact the management account administra -When you subscribed new users, Amazon Q created the following AWS resources on your behalf in your member account: +When you subscribed users in your member account, Amazon Q created the following AWS resources on your behalf: @@ -151 +147,5 @@ You can't convert or merge an account instance of IAM Identity Center into an or - * **A managed application** called **QDefaultProfile** , in IAM Identity Center. The application enables a settings profile (see the next bullet for details). The application is created once and shared between all Amazon Q Developer Pro subscribers in your account. + * **A managed application** called **QDefaultProfile** , in IAM Identity Center. The application enables a settings profile (see the next bullet for details). The application is created once and shared between all Amazon Q Developer Pro subscribers in your member account. + +###### Note + +You can install the **QDefaultProfile** managed application in a maximum of 50 AWS accounts within an organization.