AWS quicksight documentation change
Summary
Updated product name references from 'Quick Suite' to 'Quick' throughout the documentation
Security assessment
Changes are purely cosmetic rebranding (name shortening) without modifying security functionality. The VPC endpoint security mechanisms remain unchanged, and there's no evidence of vulnerability fixes.
Diff
diff --git a/quicksight/latest/developerguide/vpc-interface-endpoints.md b/quicksight/latest/developerguide/vpc-interface-endpoints.md index 41c8affc0..d2b029e4e 100644 --- a//quicksight/latest/developerguide/vpc-interface-endpoints.md +++ b//quicksight/latest/developerguide/vpc-interface-endpoints.md @@ -7 +7 @@ Considerations for Quick Suite VPC endpointsCreating an interface VPC endpoint f -# Quick Suite and interface VPC endpoints (AWS PrivateLink) +# Quick and interface VPC endpoints (AWS PrivateLink) @@ -9 +9 @@ Considerations for Quick Suite VPC endpointsCreating an interface VPC endpoint f -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 Quick Suite website and APIs without leaving the Amazon network. Instances in your VPC don't need public IP addresses to communicate with Quick Suite website and APIs, but still need access to certain domains other than Quick Suite so that static assets, reports, and other files can be downloaded. For a list of domains that Quick Suite needs to access, see Domains accessed by Quick Suite. +You can establish a private connection between your VPC and Quick 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 Quick Suite website and APIs without leaving the Amazon network. Instances in your VPC don't need public IP addresses to communicate with Quick Suite website and APIs, but still need access to certain domains other than Quick Suite so that static assets, reports, and other files can be downloaded. For a list of domains that Quick Suite needs to access, see Domains accessed by Quick Suite. @@ -21 +21 @@ The following considerations apply to VPC endpoint restrictions in Quick Suite: - * Quick Suite supports data sources from AWS services including Amazon S3, Amazon Redshift, and Athena. Quick Suite 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 Quick Suite account is configured to. For more information about connecting to a VPC connection with Quick Suite, see [Connecting to a VPC with Quick Suite](https://docs.aws.amazon.com/quicksight/latest/user/working-with-aws-vpc.html). + * Quick Suite supports data sources from AWS services including Amazon S3, Amazon Redshift, and Athena. Quick Suite 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 Quick Suite account is configured to. For more information about connecting to a VPC connection with Quick Suite, see [Connecting to a VPC with Quick](https://docs.aws.amazon.com/quicksight/latest/user/working-with-aws-vpc.html). @@ -181 +181 @@ The following is an example of an endpoint policy for Quick Suite APIs. When att -You can choose to restrict access to your Quick Suite account to only allow traffic from an approved VPC endpoint. This prevents general internet users from accessing your Quick Suite 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). +You can choose to restrict access to your Quick Suite account to only allow traffic from an approved VPC endpoint. This prevents general internet users from accessing your Quick Suite 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](https://docs.aws.amazon.com/quicksight/latest/user/enabling-ip-restrictions.html). @@ -207 +207 @@ You can also perform this action with the Quick Suite APIs. The following exampl -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 domains listed in the table. +The table below lists all URLs that are accessed by Quick from your browser. Make sure that you have established connectivity for all of domains listed in the table.