AWS singlesignon documentation change
Summary
Clarified AWS managed application deployment requirements across Regions and added reference to applications support table. Minor capitalization fix for 'customer managed applications'.
Security assessment
Changes focus on deployment prerequisites and documentation structure improvements. No security vulnerabilities or security feature enhancements are mentioned.
Diff
diff --git a/singlesignon/latest/userguide/multi-region-application-use.md b/singlesignon/latest/userguide/multi-region-application-use.md index c50a6d5f6..ab4fb6b3d 100644 --- a//singlesignon/latest/userguide/multi-region-application-use.md +++ b//singlesignon/latest/userguide/multi-region-application-use.md @@ -15 +15,3 @@ With a single-Region IAM Identity Center instance, you can deploy AWS managed ap -A multi-Region IAM Identity Center instance lets you deploy AWS managed applications in any enabled Region with a connection to IAM Identity Center in the same Region ("Region-local connection"). This requires that the AWS managed application is available in the Region and supports deployment in additional Regions. With a Region-local connection to IAM Identity Center, AWS managed applications access workforce identities in the same Region for optimal performance and reliability. We recommend choosing a Region-local connection when deploying an AWS managed application whenever the [prerequisites](./multi-region-iam-identity-center.html#multi-region-prerequisites) are met. +A multi-Region IAM Identity Center instance lets you deploy AWS managed applications in any enabled Region with a connection to IAM Identity Center in the same Region ("Region-local connection"). Deployment in the primary Region is supported by all integrated AWS managed applications. To confirm which AWS managed applications support deployment in additional Regions of IAM Identity Center, see the applications table in [AWS managed applications that you can use with IAM Identity Center](./awsapps-that-work-with-identity-center.html). In any case, the AWS managed application has to be available in the Region where you want to deploy it. + +With a Region-local connection to IAM Identity Center, AWS managed applications access workforce identities in the same Region for optimal performance and reliability. We recommend choosing a Region-local connection when deploying an AWS managed application whenever the [prerequisites](./multi-region-iam-identity-center.html#multi-region-prerequisites) are met. @@ -54 +56 @@ Each AWS managed application connects to a specific IAM Identity Center Region d -IAM Identity Center supports SAML and OAuth2 [Customer managed applications](./customermanagedapps.html). You can choose to create them in any enabled Region of your IAM Identity Center instance. After you create one, you manage the application and its assignments to users and groups in the same Region. +IAM Identity Center supports SAML and OAuth2 [customer managed applications](./customermanagedapps.html). You can choose to create them in any enabled Region of your IAM Identity Center instance. After you create one, you manage the application and its assignments to users and groups in the same Region.