AWS managedservices documentation change
Summary
Updated documentation to replace all instances of 'QuickSight' with 'Quick Suite' as the service name reference
Security assessment
The change appears to be a branding update from QuickSight to Quick Suite with no security context. No security controls, vulnerabilities, or security features are mentioned or modified in the documentation changes.
Diff
diff --git a/managedservices/latest/accelerate-guide/tr-qs-integration.md b/managedservices/latest/accelerate-guide/tr-qs-integration.md index 50c98f601..6fdb437b6 100644 --- a//managedservices/latest/accelerate-guide/tr-qs-integration.md +++ b//managedservices/latest/accelerate-guide/tr-qs-integration.md @@ -7 +7 @@ Add a new dataset for the Remediation item logAdd a new dataset for the Automate -# Trusted Remediator integration with QuickSight +# Trusted Remediator integration with Quick Suite @@ -9 +9 @@ Add a new dataset for the Remediation item logAdd a new dataset for the Automate -You can integrate the Trusted Remediator logs stored in Amazon S3 with QuickSight to build customized remediation report. QuickSight integration is optional. This feature allows you to use the logs to build custom reporting dashboards. To obtain on-request reports for Trusted Remediator, contact your CSDM. For more information on available Trusted Remediator reports, see [Trusted Remediator reports](./trusted-remediator-reports.html). +You can integrate the Trusted Remediator logs stored in Amazon S3 with Quick Suite to build customized remediation report. Quick Suite integration is optional. This feature allows you to use the logs to build custom reporting dashboards. To obtain on-request reports for Trusted Remediator, contact your CSDM. For more information on available Trusted Remediator reports, see [Trusted Remediator reports](./trusted-remediator-reports.html). @@ -11 +11 @@ You can integrate the Trusted Remediator logs stored in Amazon S3 with QuickSigh -For more information on visualizing data in QuickSight, see [Visualizing data in QuickSight](https://docs.aws.amazon.com/quicksight/latest/user/working-with-visuals.html). +For more information on visualizing data in Quick Suite, see [Visualizing data in Quick Suite](https://docs.aws.amazon.com/quicksight/latest/user/working-with-visuals.html). @@ -13 +13 @@ For more information on visualizing data in QuickSight, see [Visualizing data in -## Add a dataset to QuickSight for the Remediation item log +## Add a dataset to Quick Suite for the Remediation item log @@ -15 +15 @@ For more information on visualizing data in QuickSight, see [Visualizing data in -To add a dataset to QuickSight for the Remediation item log, follow these steps: +To add a dataset to Quick Suite for the Remediation item log, follow these steps: @@ -17 +17 @@ To add a dataset to QuickSight for the Remediation item log, follow these steps: - 1. Log in to QuickSight console. You can create the QuickSight report in any AWS Region that QuickSight supports. However, for better performance and lower costs, it's a best practice to create the report in the Region where the Trusted Remediator logging bucket is located. + 1. Log in to Quick Suite console. You can create the Quick Suite report in any AWS Region that QuickSight supports. However, for better performance and lower costs, it's a best practice to create the report in the Region where the Trusted Remediator logging bucket is located. @@ -59 +59 @@ The following is a sample analysis: -## Add a dataset to QuickSight for the Automated remediation execution log +## Add a dataset to Quick Suite for the Automated remediation execution log @@ -61 +61 @@ The following is a sample analysis: - 1. Log in to QuickSight console. You can create the QuickSight report in any AWS Region that QuickSight supports. However, for better performance and lower costs, it's a best practice to create the report in the Region where the Trusted Remediator logging bucket is located. + 1. Log in to Quick Suite console. You can create the Quick Suite report in any AWS Region that QuickSight supports. However, for better performance and lower costs, it's a best practice to create the report in the Region where the Trusted Remediator logging bucket is located.