AWS quicksight medium security documentation change
Summary
Added documentation for VPC endpoints supporting Quick Suite APIs, expanded endpoint policy examples, updated domain requirements, and restructured content to separate website vs API configurations
Security assessment
The changes introduce VPC endpoint support for Quick Suite APIs (previously unsupported) and demonstrate how to create restrictive endpoint policies for API access. This enables private network access for API calls and shows security controls through policy conditions like PrincipalAccount restrictions. The addition of FIPS endpoint documentation also indicates compliance considerations.
Diff
diff --git a/quicksight/latest/developerguide/vpc-interface-endpoints.md b/quicksight/latest/developerguide/vpc-interface-endpoints.md index 0ddd7a0ee..88e6ec8bb 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 SuiteCreating a VPC endpoint policy for Quick SuiteRestricting access to the Quick Suite websiteDomains accessed by Quick Suite +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 @@ -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 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. +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. @@ -21,2 +20,0 @@ The following considerations apply to VPC endpoint restrictions in Quick Suite: - * 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. - @@ -27,3 +25 @@ The following considerations apply to VPC endpoint restrictions in Quick Suite: - * Quick Suite VPC endpoints are not available in China regions. - - * Quick Suite VPC endpoints are not available in GovCloud regions. + * Quick Suite Website VPC endpoints are not available in China regions & Govcloud. @@ -34 +30 @@ The following considerations apply to VPC endpoint restrictions in Quick Suite: -## Creating an interface VPC endpoint for Quick Suite +## Creating an interface VPC endpoint for Quick Suite Website @@ -38 +34 @@ You can create a VPC endpoint for the Quick Suite website using either the Amazo -Create a VPC endpoint for Quick Suite using the following service name: +Create VPC endpoints for Quick Suite using the following service names: @@ -40 +36 @@ Create a VPC endpoint for Quick Suite using the following service name: - * `com.amazonaws.`region`.quicksight-website` + * `com.amazonaws.`region`.quicksight-website` \- For Quick Suite website access @@ -58 +54 @@ For more information about VPC endpoints for the AWS Management Console, see [Re -## Creating a VPC endpoint policy for Quick Suite +## Creating a VPC endpoint policy for Quick Suite Website @@ -73 +69 @@ For more information, see [Controlling access to services with VPC endpoints](ht -###### Example: VPC endpoint policy for Quick Suite actions +###### Example: VPC endpoint policy for Quick Suite Website actions @@ -104 +100,78 @@ 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 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 and API calls after the user signs in. + +## Creating an interface VPC endpoint for Quick Suite APIs + +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_. + +Create VPC endpoints for Quick Suite using the following service names: + + * `com.amazonaws.`region`.quicksight` + + * For Quick Suite API access through FIPS endpoint- `com.amazonaws.`region`.quicksight-fips` + + + + +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. + +For more information about VPC endpoints for the AWS Management Console, see [Required VPC endpoints and DNS configuration](https://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/required-endpoints-dns-configuration.html). + +###### Following APIs are not supported via interface VPC endpoint Quick Suite API: + +API Name +--- +CreateActionConnector +DeleteActionConnector +DescribeActionConnector +DescribeActionConnectorPermissions +ListActionConnectors +SearchActionConnectors +UpdateActionConnector +UpdateActionConnectorPermissions +GetFlowMetadata +GetFlowPermissions +ListFlows +SearchFlows +UpdateFlowPermissions + +## Creating a VPC endpoint policy for Quick Suite APIs + +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: + + * The principal that can perform actions. + + * The actions that can be performed. + + * The resources on which actions can be performed. + + + + +For more information, see [Controlling access to services with VPC endpoints](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints-access.html) in the _Amazon VPC User Guide_. + +###### Example: VPC endpoint policy for Quick Suite API actions + +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. + + + { + "Version":"2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Principal": "*", + "Action": [ + "quicksight:DescribeUser", + "quicksight:ListUsers" + ], + "Resource": "*", + "Condition": { + "StringEquals": { + "aws:PrincipalAccount": [ + "012345678901" + ] + } + } + } + ] + } @@ -138,0 +212 @@ region.quicksight.aws.amazon.com | The bulk of traffic to Quick Suite flows thr +quicksight.region.amazonaws.com | Quick Suite public API calls. | Yes @@ -141 +215 @@ region.signin.aws | To sign in to the AWS console if the account uses or Quick -*.cloudfront.net | To download static assets, for example CSS orr JS. | No +*.cloudfront.net | To download static assets, for example CSS or JS. | No @@ -143,0 +218,7 @@ region.signin.aws | To sign in to the AWS console if the account uses or Quick +https://*.kinesisvideo.amazonaws.com | To allow live streaming of automation workflows | No +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