Browse through the questions and answers listed below or filter and sort to narrow down your results.
Source IP using PrivateLink and NLB
Setup: Server1 (VPC-A) -> PrivateLink (VPC-B)-> NLB (VPC-B) -> Server2 (VPC-B) The application (server 2) needs to know the source IP of the consumer (server 1). What will be the visible source IP on server2? Is it the private IP of server1 or the NLB if not, then how can we get it?
Is there a cost for the data transfer between Redshift and QuickSight
Hello, in the case a customer uses QuickSight to Access data within a VPC (as in https://docs.aws.amazon.com/quicksight/latest/user/working-with-aws-vpc.html) on which, for example, redshift is running, will the customer be charged for data transfer out of the the VPC. If yes, will the cost be based on the PrivateLink price, the Internet price or another price Thanks a lot
Multi Account Connectivity using PrivateLink and/or Transit Gateway along with Direct Connect
One of my customer want to connect with their customers in the following scenarios:- Scenario with their Customer A Their Customer A has a Direct Connect and they need to get connectivity to private APIs that are in their Customer A's on premise data center. I think they can use PrivateLink. Need confirmation/validation and also things to watch out for (things that might not be supported etc.). https://aws.amazon.com/blogs/aws/aws-privatelink-update-vpc-endpoints-for-your-own-applications-services/ Scenario with their Customer B Their Customer B has a Direct Connect and wants to leverage Transit Gateway with multiple VPC to achieve something similar. Again need validation if this approach works and things to watch out for. https://aws.amazon.com/blogs/aws/use-aws-transit-gateway-direct-connect-to-centralize-and-streamline-your-network-connectivity/ Also, what should be our recommended option or pros and cons of the two solutions.
Accessing a RDS database in another account using AWS PrivateLink
A customer wants to access a DB Instance in a VPC from an EC2 Instance in a different VPC. They are currently using VPC Peering for this as documented here: [USER_VPC.Scenarios] They would like to know if they could instead use a VPC endpoint as documented here: [endpoint-service] Is it possible to make the RDS database available in the other VPC using a NLB and a PrivateLink? What would be the impacts? The limits? : https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.Scenarios.html#USER_VPC.Scenario3 : https://docs.aws.amazon.com/vpc/latest/userguide/endpoint-service.html
Does the IP address created for PrivateLink Interface Endpoint can change?
A customer is interested in adding the IP addresses assigned to a VPC Interface Endpoint to an ALB target group. They have tested and it is working fine. They are concerned tough that the Interface Endpoint IP address might eventually be changed by AWS.
Private link access over direct connect - Direct Connect Gateway
Privatelink (Endpoint services) states support for connections over Direct Connect. I'd like confirmation that this also applies in the cases where the customer's direct connect plugs in Direct Connect Gateway rather than having the VIF plugged directly in the VPC. Scenario Customer A (service provider) exposes SaaS as a privatelink to customer B (service consumer). Customer B requires private connectivity (governance) so they will provision an AWS account and DX for that purpose - rather than just creating the vif and attaching it to the VPC , customer B will connect it to a DX gateway and create the vif at the other side to the VPC, if customer A SaaS needs to DR to another region customer B can also 'DR' their connectivity to the same DR region as the SaaS app. Valid setup/solution?