AWS quicksight documentation change
Summary
Updated documentation to replace 'QuickSight' with 'Quick Suite' terminology throughout the VPC interface endpoints guide
Security assessment
The changes are purely terminological updates from 'QuickSight' to 'Quick Suite' without altering security guidance or addressing vulnerabilities. The content still describes the same VPC endpoint configuration process using AWS PrivateLink, which is a security feature, but no new security documentation is added.
Diff
diff --git a/quicksight/latest/developerguide/vpc-interface-endpoints.md b/quicksight/latest/developerguide/vpc-interface-endpoints.md index 674296f19..28a4574a4 100644 --- a//quicksight/latest/developerguide/vpc-interface-endpoints.md +++ b//quicksight/latest/developerguide/vpc-interface-endpoints.md @@ -5 +5 @@ -Considerations for QuickSight VPC endpointsCreating an interface VPC endpoint for QuickSightCreating a VPC endpoint policy for QuickSightRestricting access to the QuickSight websiteDomains accessed by QuickSight +Considerations for Quick Suite VPC endpointsCreating an interface VPC endpoint for Quick SuiteCreating a VPC endpoint policy for Quick SuiteRestricting access to the Quick Suite websiteDomains accessed by Quick Suite @@ -9 +9 @@ Considerations for QuickSight VPC endpointsCreating an interface VPC endpoint fo -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. +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 without leaving the Amazon network. Instances in your VPC don't need public IP addresses to communicate with Quick Suite website, 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. @@ -15 +15 @@ For more information, see [Interface VPC endpoints (AWS PrivateLink)](https://do -## Considerations for QuickSight VPC endpoints +## Considerations for Quick Suite VPC endpoints @@ -17 +17 @@ For more information, see [Interface VPC endpoints (AWS PrivateLink)](https://do -Before you set up an interface VPC endpoint for QuickSight, 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 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_. @@ -19 +19 @@ Before you set up an interface VPC endpoint for QuickSight, ensure that you revi -The following considerations apply to VPC endpoint restrictions in QuickSight: +The following considerations apply to VPC endpoint restrictions in Quick Suite: @@ -21 +21 @@ The following considerations apply to VPC endpoint restrictions in QuickSight: - * The VPC endpoint that you create for QuickSight only works for the QuickSight website. QuickSight API calls are not supported through VPC endpoints. + * The VPC endpoint that you create for Quick Suite only works for the Quick Suite website. Quick Suite API calls are not supported through VPC endpoints. @@ -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 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 Suite](https://docs.aws.amazon.com/quicksight/latest/user/working-with-aws-vpc.html). @@ -25 +25 @@ The following considerations apply to VPC endpoint restrictions in QuickSight: - * IP and VPC endpoint rules precede all other rules in QuickSight. If you have embedded dashboards or visuals that are visible to the public (anyone on the internet) and restrict traffic to the QuickSight 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 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). @@ -27 +27 @@ The following considerations apply to VPC endpoint restrictions in QuickSight: - * QuickSight VPC endpoints are not available in China regions. + * Quick Suite VPC endpoints are not available in China regions. @@ -29 +29 @@ The following considerations apply to VPC endpoint restrictions in QuickSight: - * QuickSight VPC endpoints are not available in GovCloud regions. + * Quick Suite VPC endpoints are not available in GovCloud regions. @@ -34 +34 @@ The following considerations apply to VPC endpoint restrictions in QuickSight: -## Creating an interface VPC endpoint for QuickSight +## Creating an interface VPC endpoint for Quick Suite @@ -36 +36 @@ The following considerations apply to VPC endpoint restrictions in QuickSight: -You can create a VPC endpoint for the QuickSight 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 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_. @@ -38 +38 @@ You can create a VPC endpoint for the QuickSight website using either the Amazon -Create a VPC endpoint for QuickSight using the following service name: +Create a VPC endpoint for Quick Suite using the following service name: @@ -45 +45 @@ Create a VPC endpoint for QuickSight using the following service name: -The private DNS names for the QuickSight website are not same as the public URL for QuickSight. To reach QuickSight 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 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). @@ -47 +47 @@ The private DNS names for the QuickSight website are not same as the public URL -The management of certain administrator features require that an administrator sign in to QuickSight 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 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. @@ -58 +58 @@ For more information about VPC endpoints for the AWS Management Console, see [Re -## Creating a VPC endpoint policy for QuickSight +## Creating a VPC endpoint policy for Quick Suite @@ -60 +60 @@ 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 QuickSight 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 QuickSight 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 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: @@ -73 +73 @@ For more information, see [Controlling access to services with VPC endpoints](ht -###### Example: VPC endpoint policy for QuickSight actions +###### Example: VPC endpoint policy for Quick Suite actions @@ -75 +75 @@ For more information, see [Controlling access to services with VPC endpoints](ht -The following is an example of an endpoint policy for QuickSight. When attached to an endpoint, this policy grants access to all QuickSight actions for all principals on all resources. +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. @@ -104 +104 @@ JSON -Policies for the QuickSight 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 QuickSight website after the user signs in. +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 after the user signs in. @@ -106 +106 @@ Policies for the QuickSight website must have the values of the `Principal`, `Ac -## Restricting access to the QuickSight website +## Restricting access to the Quick Suite website @@ -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 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 Suite](https://docs.aws.amazon.com/quicksight/latest/user/enabling-ip-restrictions.html). @@ -110 +110 @@ You can choose to restrict access to your QuickSight account to only allow traff -Use the following procedure to restrict access with a VPC endpoint in QuickSight. +Use the following procedure to restrict access with a VPC endpoint in Quick Suite. @@ -112 +112 @@ Use the following procedure to restrict access with a VPC endpoint in QuickSight - 1. Open the [QuickSight console](https://quicksight.aws.amazon.com/). + 1. Open the [Quick Suite console](https://quicksight.aws.amazon.com/). @@ -114 +114 @@ Use the following procedure to restrict access with a VPC endpoint in QuickSight - 2. Choose **Manage QuickSight** , and then choose **Security & permissions**. + 2. Choose **Manage Quick Suite** , and then choose **Security & permissions**. @@ -123 +123 @@ Use the following procedure to restrict access with a VPC endpoint in QuickSight -You can also perform this action with the QuickSight APIs. The following example turns on the enforcement of a VPC endpoint restriction. +You can also perform this action with the Quick Suite APIs. The following example turns on the enforcement of a VPC endpoint restriction. @@ -132 +132 @@ You can also perform this action with the QuickSight APIs. The following example -## Domains accessed by QuickSight +## Domains accessed by Quick Suite @@ -138 +138 @@ URL | Reason | Has VPC endpoint support? -region.quicksight.aws.amazon.com | The bulk of traffic to QuickSight flows through this domain. | Yes +region.quicksight.aws.amazon.com | The bulk of traffic to Quick Suite flows through this domain. | Yes @@ -140 +140 @@ 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 QuickSight native users for identity management. | No +region.signin.aws | To sign in to the AWS console if the account uses or Quick Suite native users for identity management. | No