AWS quicksight documentation change
Summary
Updated documentation to replace 'Quick Suite' with 'Quick' throughout the file, including references to websites, APIs, and terminology. No functional changes to VPC endpoint setup instructions.
Security assessment
The changes are purely branding/terminology updates from 'Quick Suite' to 'Quick'. There are no modifications to security configurations, vulnerability fixes, or new security guidance. The existing security context about VPC endpoints and access restrictions remains unchanged.
Diff
diff --git a/quicksight/latest/developerguide/vpc-interface-endpoints.md b/quicksight/latest/developerguide/vpc-interface-endpoints.md index d2b029e4e..c546220b5 100644 --- a//quicksight/latest/developerguide/vpc-interface-endpoints.md +++ b//quicksight/latest/developerguide/vpc-interface-endpoints.md @@ -5 +5 @@ -Considerations for Quick Suite VPC endpointsCreating an interface VPC endpoint for Quick Suite WebsiteCreating a VPC endpoint policy for Quick Suite WebsiteCreating an interface VPC endpoint for Quick Suite APIsCreating a VPC endpoint policy for Quick Suite APIsRestricting access to the Quick Suite websiteDomains accessed by Quick Suite +Considerations for Quick VPC endpointsCreating an interface VPC endpoint for Quick WebsiteCreating a VPC endpoint policy for Quick WebsiteCreating an interface VPC endpoint for Quick APIsCreating a VPC endpoint policy for Quick APIsRestricting access to the Quick websiteDomains accessed by Quick @@ -9 +9 @@ Considerations for Quick Suite VPC endpointsCreating an interface VPC endpoint f -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. +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 website and APIs without leaving the Amazon network. Instances in your VPC don't need public IP addresses to communicate with Quick website and APIs, but still need access to certain domains other than Quick so that static assets, reports, and other files can be downloaded. For a list of domains that Quick needs to access, see Domains accessed by Quick. @@ -15 +15 @@ For more information, see [Interface VPC endpoints (AWS PrivateLink)](https://do -## Considerations for Quick Suite VPC endpoints +## Considerations for Quick VPC endpoints @@ -17 +17 @@ For more information, see [Interface VPC endpoints (AWS PrivateLink)](https://do -Before you set up an interface VPC endpoint for Quick Suite, ensure that you review [Interface endpoint properties and limitations](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#vpce-interface-limitations) in the _Amazon VPC User Guide_. +Before you set up an interface VPC endpoint for Quick, ensure that you review [Interface endpoint properties and limitations](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#vpce-interface-limitations) in the _Amazon VPC User Guide_. @@ -19 +19 @@ Before you set up an interface VPC endpoint for Quick Suite, ensure that you rev -The following considerations apply to VPC endpoint restrictions in Quick Suite: +The following considerations apply to VPC endpoint restrictions in Quick: @@ -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](https://docs.aws.amazon.com/quicksight/latest/user/working-with-aws-vpc.html). + * Quick supports data sources from AWS services including Amazon S3, Amazon Redshift, and Athena. Quick 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 account is configured to. For more information about connecting to a VPC connection with Quick, see [Connecting to a VPC with Quick](https://docs.aws.amazon.com/quicksight/latest/user/working-with-aws-vpc.html). @@ -23 +23 @@ The following considerations apply to VPC endpoint restrictions in Quick Suite: - * IP and VPC endpoint rules precede all other rules in Quick Suite. If you have embedded dashboards or visuals that are visible to the public (anyone on the internet) and restrict traffic to the Quick Suite website through a VPC endpoint, public dashboards can only be shared through the VPC endpoint. For more information on public embedding, see [Turning on public access to visuals and dashboards with a 1-click embed code](https://docs.aws.amazon.com/quicksight/latest/user/embedded-analytics-1-click-public.html). + * IP and VPC endpoint rules precede all other rules in Quick. If you have embedded dashboards or visuals that are visible to the public (anyone on the internet) and restrict traffic to the Quick website through a VPC endpoint, public dashboards can only be shared through the VPC endpoint. For more information on public embedding, see [Turning on public access to visuals and dashboards with a 1-click embed code](https://docs.aws.amazon.com/quicksight/latest/user/embedded-analytics-1-click-public.html). @@ -25 +25 @@ The following considerations apply to VPC endpoint restrictions in Quick Suite: - * Quick Suite Website VPC endpoints are not available in China regions & Govcloud. + * Quick Website VPC endpoints are not available in China regions & Govcloud. @@ -30 +30 @@ The following considerations apply to VPC endpoint restrictions in Quick Suite: -## Creating an interface VPC endpoint for Quick Suite Website +## Creating an interface VPC endpoint for Quick Website @@ -32 +32 @@ The following considerations apply to VPC endpoint restrictions in Quick Suite: -You can create a VPC endpoint for the Quick Suite website using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Creating an interface endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#create-interface-endpoint) in the _Amazon VPC User Guide_. +You can create a VPC endpoint for the Quick website using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Creating an interface endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#create-interface-endpoint) in the _Amazon VPC User Guide_. @@ -34 +34 @@ You can create a VPC endpoint for the Quick Suite website using either the Amazo -Create VPC endpoints for Quick Suite using the following service names: +Create VPC endpoints for Quick using the following service names: @@ -36 +36 @@ Create VPC endpoints for Quick Suite using the following service names: - * `com.amazonaws.`region`.quicksight-website` \- For Quick Suite website access + * `com.amazonaws.`region`.quicksight-website` \- For Quick website access @@ -41 +41 @@ Create VPC endpoints for Quick Suite using the following service names: -The private DNS names for the Quick Suite website are not same as the public URL for Quick Suite. To reach Quick Suite through the public URL, create an A record for the website in the format `<region>.quicksight.aws.amazon.com` and point it to the VPC endpoint. For more information about routing to a VPC endpoint, see [Routing traffic to an Amazon Virtual Private Cloud interface endpoint by using your domain name](https://docs.aws.amazon.com//Route53/latest/DeveloperGuide/routing-to-vpc-interface-endpoint.html). +The private DNS names for the Quick website are not same as the public URL for Quick. To reach Quick through the public URL, create an A record for the website in the format `<region>.quicksight.aws.amazon.com` and point it to the VPC endpoint. For more information about routing to a VPC endpoint, see [Routing traffic to an Amazon Virtual Private Cloud interface endpoint by using your domain name](https://docs.aws.amazon.com//Route53/latest/DeveloperGuide/routing-to-vpc-interface-endpoint.html). @@ -43 +43 @@ The private DNS names for the Quick Suite website are not same as the public URL -The management of certain administrator features require that an administrator sign in to Quick Suite as an IAM user. If you sign in through the VPC endpoint, you need to create the following VPC endpoints for the AWS Management Console. +The management of certain administrator features require that an administrator sign in to Quick as an IAM user. If you sign in through the VPC endpoint, you need to create the following VPC endpoints for the AWS Management Console. @@ -54 +54 @@ For more information about VPC endpoints for the AWS Management Console, see [Re -## Creating a VPC endpoint policy for Quick Suite Website +## Creating a VPC endpoint policy for Quick Website @@ -56 +56 @@ For more information about VPC endpoints for the AWS Management Console, see [Re -You can attach an endpoint policy to your VPC endpoint to restrict usage of the endpoint to specific Quick Suite accounts or to accounts under specific AWS organizations. The AWS account IDs that are allow–listed or deny–listed are the AWS accounts in which the Quick Suite account is created. In most cases, this is the same account ID in which the VPC endpoint is created. The policy specifies the following information: +You can attach an endpoint policy to your VPC endpoint to restrict usage of the endpoint to specific Quick accounts or to accounts under specific AWS organizations. The AWS account IDs that are allow–listed or deny–listed are the AWS accounts in which the Quick account is created. In most cases, this is the same account ID in which the VPC endpoint is created. The policy specifies the following information: @@ -69 +69 @@ For more information, see [Controlling access to services with VPC endpoints](ht -###### Example: VPC endpoint policy for Quick Suite Website actions +###### Example: VPC endpoint policy for Quick Website actions @@ -71 +71 @@ For more information, see [Controlling access to services with VPC endpoints](ht -The following is an example of an endpoint policy for Quick Suite. When attached to an endpoint, this policy grants access to all Quick Suite actions for all principals on all resources. +The following is an example of an endpoint policy for Quick. When attached to an endpoint, this policy grants access to all Quick actions for all principals on all resources. @@ -100 +100 @@ JSON -Policies for the Quick Suite website must have the values of the `Principal`, `Action`, and `Resource` fields set to `"*"`. A condition may be specified only against the `aws:PrincipalAccount` or the `aws:OrgId attributes`. These conditions are evaluated on all requests to the Quick Suite website and API calls after the user signs in. +Policies for the Quick website must have the values of the `Principal`, `Action`, and `Resource` fields set to `"*"`. A condition may be specified only against the `aws:PrincipalAccount` or the `aws:OrgId attributes`. These conditions are evaluated on all requests to the Quick website and API calls after the user signs in. @@ -102 +102 @@ Policies for the Quick Suite website must have the values of the `Principal`, `A -## Creating an interface VPC endpoint for Quick Suite APIs +## Creating an interface VPC endpoint for Quick APIs @@ -104 +104 @@ Policies for the Quick Suite website must have the values of the `Principal`, `A -You can create a VPC endpoint for the Quick Suite APIs using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Creating an interface endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#create-interface-endpoint) in the _Amazon VPC User Guide_. +You can create a VPC endpoint for the Quick APIs using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Creating an interface endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#create-interface-endpoint) in the _Amazon VPC User Guide_. @@ -106 +106 @@ You can create a VPC endpoint for the Quick Suite APIs using either the Amazon V -Create VPC endpoints for Quick Suite using the following service names: +Create VPC endpoints for Quick using the following service names: @@ -110 +110 @@ Create VPC endpoints for Quick Suite using the following service names: - * For Quick Suite API access through FIPS endpoint- `com.amazonaws.`region`.quicksight-fips` + * For Quick API access through FIPS endpoint- `com.amazonaws.`region`.quicksight-fips` @@ -115 +115 @@ Create VPC endpoints for Quick Suite using the following service names: -When you create a VPC endpoint for Quick Suite APIs, the private DNS resolution automatically routes API calls to the VPC endpoint. No additional DNS configuration is required - your existing API calls to `quicksight.<region>.amazonaws.com` will automatically use the VPC endpoint when private DNS is enabled. +When you create a VPC endpoint for Quick APIs, the private DNS resolution automatically routes API calls to the VPC endpoint. No additional DNS configuration is required - your existing API calls to `quicksight.<region>.amazonaws.com` will automatically use the VPC endpoint when private DNS is enabled. @@ -119 +119 @@ For more information about VPC endpoints for the AWS Management Console, see [Re -###### Following APIs are not supported via interface VPC endpoint Quick Suite API: +###### Following APIs are not supported via interface VPC endpoint Quick API: @@ -137 +137 @@ UpdateFlowPermissions -## Creating a VPC endpoint policy for Quick Suite APIs +## Creating a VPC endpoint policy for Quick APIs @@ -139 +139 @@ UpdateFlowPermissions -You can attach an endpoint policy to your VPC endpoint to restrict usage of the endpoint to specific Quick Suite accounts or to accounts under specific AWS organizations. The AWS account IDs that are allow–listed or deny–listed are the AWS accounts in which the Quick Suite account is created. In most cases, this is the same account ID in which the VPC endpoint is created. The policy specifies the following information: +You can attach an endpoint policy to your VPC endpoint to restrict usage of the endpoint to specific Quick accounts or to accounts under specific AWS organizations. The AWS account IDs that are allow–listed or deny–listed are the AWS accounts in which the Quick account is created. In most cases, this is the same account ID in which the VPC endpoint is created. The policy specifies the following information: @@ -152 +152 @@ For more information, see [Controlling access to services with VPC endpoints](ht -###### Example: VPC endpoint policy for Quick Suite API actions +###### Example: VPC endpoint policy for Quick API actions @@ -154 +154 @@ For more information, see [Controlling access to services with VPC endpoints](ht -The following is an example of an endpoint policy for Quick Suite APIs. When attached to an endpoint, this policy grants access to all Quick Suite actions for specific Quick Suite actions and conditions. +The following is an example of an endpoint policy for Quick APIs. When attached to an endpoint, this policy grants access to all Quick actions for specific Quick actions and conditions. @@ -179 +179 @@ The following is an example of an endpoint policy for Quick Suite APIs. When att -## Restricting access to the Quick Suite website +## Restricting access to the Quick website @@ -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](https://docs.aws.amazon.com/quicksight/latest/user/enabling-ip-restrictions.html). +You can choose to restrict access to your Quick account to only allow traffic from an approved VPC endpoint. This prevents general internet users from accessing your Quick 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). @@ -183 +183 @@ You can choose to restrict access to your Quick Suite account to only allow traf -Use the following procedure to restrict access with a VPC endpoint in Quick Suite. +Use the following procedure to restrict access with a VPC endpoint in Quick. @@ -185 +185 @@ Use the following procedure to restrict access with a VPC endpoint in Quick Suit - 1. Open the [Quick Suite console](https://quicksight.aws.amazon.com/). + 1. Open the [Quick console](https://quicksight.aws.amazon.com/). @@ -187 +187 @@ Use the following procedure to restrict access with a VPC endpoint in Quick Suit - 2. Choose **Manage Quick Suite** , and then choose **Security & permissions**. + 2. Choose **Manage Quick** , and then choose **Security & permissions**. @@ -196 +196 @@ Use the following procedure to restrict access with a VPC endpoint in Quick Suit -You can also perform this action with the Quick Suite APIs. The following example turns on the enforcement of a VPC endpoint restriction. +You can also perform this action with the Quick APIs. The following example turns on the enforcement of a VPC endpoint restriction. @@ -205 +205 @@ You can also perform this action with the Quick Suite APIs. The following exampl -## Domains accessed by Quick Suite +## Domains accessed by Quick @@ -211,2 +211,2 @@ URL | Reason | Has VPC endpoint support? -region.quicksight.aws.amazon.com | The bulk of traffic to Quick Suite flows through this domain. | Yes -quicksight.region.amazonaws.com | Quick Suite public API calls. | Yes +region.quicksight.aws.amazon.com | The bulk of traffic to Quick flows through this domain. | Yes +quicksight.region.amazonaws.com | Quick public API calls. | Yes @@ -214 +214 @@ signin.aws.amazon.com | To sign in to the AWS console if the account uses IAM i -region.signin.aws | To sign in to the AWS console if the account uses or Quick Suite native users for identity management. | No +region.signin.aws | To sign in to the AWS console if the account uses or Quick native users for identity management. | No @@ -220,5 +220,5 @@ https://apis.google.com/js/api.js | To allow google drive file picker | NA -https://*.officeapps.live.com | To allow Quick Suite side panel extenstion | NA -https://outlook.cloud.microsoft | To allow Quick Suite side panel extenstion | NA -https://*.sharepoint.com | To allow Quick Suite side panel extenstion | NA -https://*.office.com | To allow Quick Suite side panel extenstion | NA -https://*.office365.com | To allow Quick Suite side panel extenstion | NA +https://*.officeapps.live.com | To allow Quick side panel extenstion | NA +https://outlook.cloud.microsoft | To allow Quick side panel extenstion | NA +https://*.sharepoint.com | To allow Quick side panel extenstion | NA +https://*.office.com | To allow Quick side panel extenstion | NA +https://*.office365.com | To allow Quick side panel extenstion | NA