Is there a data transfer charge between Quicksight and Redshift when using VPC Peering?

You can set up a VPC to use with QuickSight Enterprise edition. It will create logical networking component in the VPC. QuickSight creates at least two of these network interfaces to use with a VPC connection based off of the subnets that are attached to it. Then you add the VPC connection to each QuickSight data source you create. The QuickSight network interface alone doesn't give QuickSight direct access to your databases. The VPC connection works only for the QuickSight data sources that are configured to use it. When you use the QuickSight data source to query a database or other instance within your VPC, all the network traffic from QuickSight originates from this QuickSight network interface. Because the QuickSight network interface exists inside your VPC, traffic originating from it can reach destinations within your VPC by using their private IP addresses. Each QuickSight network interface gets its own private IP address that comes from the subnet you configure. The private IP address is unique for each AWS account, unlike the public IP range. If QuickSight and RedShift are in the same AZ, there will no data transfer cost since all data transfer over a VPC Peering connection that stays within an AZ is now free. But if they are in different AZ, you will be paying VPC-peering cost.