Important: We've redesigned the Amazon QuickSight analysis workspace. You might encounter screenshots or procedural text that doesn't reflect the new look in the QuickSight console. We're in the process of updating screenshots and procedural text.
To find a feature or item, use the Quick search bar.
For more information on QuickSight's new look, see Introducing new analysis experience on Amazon QuickSight
Infrastructure security in Amazon QuickSight
| Intended audience: Amazon QuickSight administrators |
Amazon QuickSight is delivered as a web application, hosted on dedicated Amazon EC2 hosts, separate from AWS virtual private clouds (VPCs). Instead of deploying QuickSight on your own hosts, you access the QuickSight service through Regional public endpoints. QuickSight accesses data sources over a secured internet connection from Regional endpoints. To access data sources that are located inside a corporate network, configure the network to allow access from one of the QuickSight public IP address blocks. We recommend that you consider using a VPC (a virtual network dedicated to your AWS account).
For more information, see the following:
As a managed service, Amazon QuickSight is protected by the AWS global network security
procedures that are described in the Amazon Web Services:
Overview of Security Processes
If you use AWS published API calls to access QuickSight through the network, clients must support Transport Layer Security (TLS) 1.0 or later. We recommend TLS 1.2 or later. Clients must also support cipher suites with perfect forward secrecy (PFS) such as Ephemeral Diffie-Hellman (DHE) or Elliptic Curve Ephemeral Diffie-Hellman (ECDHE). Most modern systems such as Java 7 and later support these modes.
Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an AWS Identity and Access Management (IAM) principal. Or you can use the AWS Security Token Service (AWS STS) to generate temporary security credentials to sign requests.
You can call these API operations from any network location, but QuickSight does support resource-based access policies, which can include restrictions based on the source IP address. You can also use QuickSight policies to control access from specific Amazon Virtual Private Cloud (Amazon VPC) endpoints or specific VPCs. Effectively, this isolates network access to a given QuickSight resource from only the specific VPC within the AWS network. For more information on using QuickSight in a VPC, see Connecting to a VPC with Amazon QuickSight.
