AWS singlesignon: Remove organization instance option for standalone AWS accounts
Summary
Corrects the guidance for standalone AWS accounts so they can create only an account instance of IAM Identity Center, dropping the previously listed organization instance option.
Security assessment
This is a documentation accuracy fix clarifying which instance type a standalone AWS account can create; it involves no misconfiguration fix or vulnerability disclosure, only correcting an inaccurate option.
Evidence
* A standalone AWS account – Use to create an [account instance](./account-instances-identity-center.html) of IAM Identity Center.
Diff
diff --git a/singlesignon/latest/userguide/identity-center-instances.md b/singlesignon/latest/userguide/identity-center-instances.md index c5f4aab..22691dd 100644 --- a//singlesignon/latest/userguide/identity-center-instances.md +++ b//singlesignon/latest/userguide/identity-center-instances.md @@ -36 +36 @@ To enable IAM Identity Center, sign in to the AWS Management Console by using on - * A standalone AWS account – Use to create an [organization instance](./organization-instances-identity-center.html) or [account instance](./account-instances-identity-center.html) of IAM Identity Center. The standalone AWS account isn't managed by AWS Organizations. You can associate only one instance of IAM Identity Center with a standalone AWS account and use that instance for application assignments within that standalone AWS account. + * A standalone AWS account – Use to create an [account instance](./account-instances-identity-center.html) of IAM Identity Center. The standalone AWS account isn't managed by AWS Organizations. You can associate only one instance of IAM Identity Center with a standalone AWS account and use that instance for application assignments within that standalone AWS account.