AWS prescriptive-guidance documentation change
Summary
Updated product name references from 'Quick Suite' to 'Quick' throughout the document, including breadcrumb navigation and content sections.
Security assessment
The changes are purely cosmetic branding updates without any security implications. No security vulnerabilities, configurations, or features are mentioned or modified. The security considerations paragraph remains unchanged except for the product name replacement.
Diff
diff --git a/prescriptive-guidance/latest/quick-suite-access-approach/conclusion.md b/prescriptive-guidance/latest/quick-suite-access-approach/conclusion.md index a606921d9..bc42cd2d2 100644 --- a//prescriptive-guidance/latest/quick-suite-access-approach/conclusion.md +++ b//prescriptive-guidance/latest/quick-suite-access-approach/conclusion.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Choosing the right access approach for Amazon Quick Suite](introduction.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Choosing the right access approach for Amazon Quick](introduction.html) @@ -7 +7 @@ -This guide reviews a number of different approaches that you can use to provision user access to Amazon Quick Suite. In some cases, you can even combine more than one approach to support different use cases. However, each additional approach adds complexity. +This guide reviews a number of different approaches that you can use to provision user access to Amazon Quick. In some cases, you can even combine more than one approach to support different use cases. However, each additional approach adds complexity. @@ -9 +9 @@ This guide reviews a number of different approaches that you can use to provisio -If all options are possible for your deployment, the recommended approach is to use the AWS IAM Identity Center built-in integration with Quick Suite. To review this approach in more detail and determine whether any of the current feature limitations apply to your situation, see [Using IAM Identity Center](https://docs.aws.amazon.com/quicksuite/latest/userguide/setting-up-sso.html) in the Quick Suite documentation. +If all options are possible for your deployment, the recommended approach is to use the AWS IAM Identity Center built-in integration with Quick. To review this approach in more detail and determine whether any of the current feature limitations apply to your situation, see [Using IAM Identity Center](https://docs.aws.amazon.com/quicksuite/latest/userguide/setting-up-sso.html) in the Quick documentation. @@ -11 +11 @@ If all options are possible for your deployment, the recommended approach is to -When you choose an approach, consider how it will affect the user sign-in experience, security, and how to support it with access management operations and processes in your organization. Switching to a different approach in the future might be costly, or it might not be possible. Before setting up Quick Suite, take the necessary time to assess what is best for your organization. +When you choose an approach, consider how it will affect the user sign-in experience, security, and how to support it with access management operations and processes in your organization. Switching to a different approach in the future might be costly, or it might not be possible. Before setting up Quick, take the necessary time to assess what is best for your organization.