AWS quicksight documentation change
Summary
Updated product name references from 'QuickSight' to 'Quick Suite' in VPC endpoint documentation and related links
Security assessment
Changes are branding updates (QuickSight → Quick Suite) without altering security guidance. VPC endpoint configuration remains the same, and no new security vulnerabilities or mitigations are introduced.
Diff
diff --git a/quicksight/latest/developerguide/vpc-interface-endpoints.md b/quicksight/latest/developerguide/vpc-interface-endpoints.md index 0a35bd8ef..674296f19 100644 --- a//quicksight/latest/developerguide/vpc-interface-endpoints.md +++ b//quicksight/latest/developerguide/vpc-interface-endpoints.md @@ -7 +7 @@ Considerations for QuickSight VPC endpointsCreating an interface VPC endpoint fo -# QuickSight and interface VPC endpoints (AWS PrivateLink) +# Quick Suite and interface VPC endpoints (AWS PrivateLink) @@ -9 +9 @@ Considerations for QuickSight VPC endpointsCreating an interface VPC endpoint fo -You can establish a private connection between your VPC and QuickSight by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access the QuickSight website without leaving the Amazon network. Instances in your VPC don't need public IP addresses to communicate with QuickSight website, but still need access to certain domains other than QuickSight so that static assets, reports, and other files can be downloaded. For a list of domains that QuickSight needs to access, see Domains accessed by QuickSight. +You can establish a private connection between your VPC and Quick Suite by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access the QuickSight website without leaving the Amazon network. Instances in your VPC don't need public IP addresses to communicate with QuickSight website, but still need access to certain domains other than QuickSight so that static assets, reports, and other files can be downloaded. For a list of domains that QuickSight needs to access, see Domains accessed by QuickSight. @@ -23 +23 @@ The following considerations apply to VPC endpoint restrictions in QuickSight: - * QuickSight supports data sources from AWS services including Amazon S3, Amazon Redshift, and Athena. QuickSight needs access to the resources from your AWS accounts to retrieve this data. If you want traffic to other AWS services to be routed through the VPC endpoint, you need to create VPC endpoint connections for each service that your QuickSight account is configured to. For more information about connecting to a VPC connection with QuickSight, see [Connecting to a VPC with QuickSight](https://docs.aws.amazon.com/quicksight/latest/user/working-with-aws-vpc.html). + * QuickSight supports data sources from AWS services including Amazon S3, Amazon Redshift, and Athena. QuickSight needs access to the resources from your AWS accounts to retrieve this data. If you want traffic to other AWS services to be routed through the VPC endpoint, you need to create VPC endpoint connections for each service that your QuickSight account is configured to. For more information about connecting to a VPC connection with QuickSight, see [Connecting to a VPC with Quick Suite](https://docs.aws.amazon.com/quicksight/latest/user/working-with-aws-vpc.html). @@ -108 +108 @@ Policies for the QuickSight website must have the values of the `Principal`, `Ac -You can choose to restrict access to your QuickSight account to only allow traffic from an approved VPC endpoint. This prevents general internet users from accessing your QuickSight account. Before you can make this change, make sure that you're an IAM user with the `UpdateIpRestriction` permission. For more information on the permissions that are required to restrict access with a VPC endpoint, see [Turning on IP and VPC endpoint restrictions in QuickSight](https://docs.aws.amazon.com/quicksight/latest/user/enabling-ip-restrictions.html). +You can choose to restrict access to your QuickSight account to only allow traffic from an approved VPC endpoint. This prevents general internet users from accessing your QuickSight account. Before you can make this change, make sure that you're an IAM user with the `UpdateIpRestriction` permission. For more information on the permissions that are required to restrict access with a VPC endpoint, see [Turning on IP and VPC endpoint restrictions in Quick Suite](https://docs.aws.amazon.com/quicksight/latest/user/enabling-ip-restrictions.html). @@ -134 +134 @@ You can also perform this action with the QuickSight APIs. The following example -The table below lists all URLs that are accessed by QuickSight from your browser. Make sure that you have established connectivity for all of domins listed in the table. +The table below lists all URLs that are accessed by Quick Suite from your browser. Make sure that you have established connectivity for all of domins listed in the table.