1 Answer
- Newest
- Most votes
- Most comments
1
You won’t need a public IP for the DCV Connection gateway instance if it is registered as a target to the ALB and is present in the same VPC as ALB, the ALB will be able to communicate to the instance via their private IP. ALB targets do not need to be public, they just need to be accessible by ALB.
Relevant content
- asked 18 days ago
- asked 2 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Hmm - we must have a configuration issue then. We have set it up as you described and it does not work until we give the DCV Gateway a public IP address. Have you tested this? We are using a ALB (application load balancer) not a NLB (network load balancer) if that makes any difference.
Typically you would have: [NICE DCV Client (thick or browser)] --tcp/udp with tls--> [NLB - typically public if you want to reach it from anywhere] -> [Connection Gateway - Private] -> [Target Virtual Desktop - Private]