MENU
A software-as-a-service (SaaS) provider hosts its solution on Amazon EC2 instances within a VPC in the AWS Cloud. All of the provider's customers also have their environments in the AWS Cloud.
A recent design meeting revealed that the customers have IP address overlap with the provider's AWS deployment. The customers have stated that they will not share their internal IP addresses and that they do not want to connect to the provider's SaaS service over the internet.
Which combination of steps is part of a solution that meets these requirements? (Choose two.)
30 comments · newest first
PA
Paz
10 months ago
Wait, can they really not share their IPs? That's a bit odd.
RO
Rocco
10 months ago
A Network Load Balancer? Seems unnecessary for this case.
RE
Rebbeca
10 months ago
I think E could work too, but not sure about the complexity.
LA
Lavera
11 months ago
Peering might not be the best option with overlapping IPs.
SH
Shanice
11 months ago
Option B is definitely a solid choice for this scenario.
YO
Yolande
11 months ago
I feel like using a Network Load Balancer could be relevant, but I can't recall if it directly addresses the IP overlap problem.
JA
Jacquelyne
11 months ago
I practiced a similar question where we had to use a Transit Gateway. It seems like E might be a good choice, but I'm not completely confident.
JE
Jenifer
11 months ago
I think option B sounds familiar; configuring an endpoint service could help with the IP overlap issue.
LE
Leatha
12 months ago
I remember something about VPC peering, but I'm not sure if it's the best option here since the customers won't share their IPs.
PR
Precious
12 months ago
Tricky one! I'm a bit unsure about the best approach, but I'll carefully review the requirements and the AWS networking services to come up with a solid solution.
JI
Jin
12 months ago
Ah, this is a classic VPC connectivity problem. I bet the Network Load Balancer or Application Load Balancer options could work well here, especially if we configure them properly.
PA
Paulene
1 year ago
Okay, so we need to keep the SaaS service isolated from the internet and allow the customers to connect privately. I'm leaning towards the endpoint service approach, but I'll double-check the other options too.
GA
Gail
1 year ago
Hmm, the IP address overlap is a key challenge here. I'm thinking an AWS Transit Gateway could be a good solution to connect the VPCs without exposing the internal IPs.
JE
Jeanice
1 year ago
This looks like a tricky one. I'll need to think through the requirements carefully and consider the different AWS networking options.
GE
Georgene
1 year ago
I think we should also consider deploying an AWS Transit Gateway to connect the SaaS VPC and share it with the customers for routing.
MI
Mica
1 year ago
Ah, the joys of IP address overlap. B and E are the way to go, unless you want to end up in a tangled web of VPC peering and routing tables.
KA
Kattie
1 year ago
Agreed, B and E seem like the most efficient options to avoid the headache of VPC peering and routing complications.
VA
Valentine
1 year ago
E) Deploy an AWS Transit Gateway, and connect the SaaS VPC to it. Share the transit gateway with the customers. Configure routing on the transit gateway.
EL
Elli
1 year ago
B) Configure an endpoint service, and grant the customers permission to create a connection to the endpoint service.
JU
Julian
1 year ago
Haha, good thing the customers don't want to use the internet. Imagine trying to troubleshoot all those NAT gateways! B and E for the win!
AL
Alexis
1 year ago
Definitely! It's great that the customers are on board with those options. It will make the setup much smoother.
FL
Fletcher
1 year ago
Yeah, NAT gateways can be a headache. Using an endpoint service and a Transit Gateway sounds like a solid solution.
LI
Lilli
1 year ago
I agree with Buck. It will help in ensuring secure connectivity without sharing internal IP addresses.
AL
Alline
1 year ago
I agree, B and E are the best choices here. Keeping the traffic off the public internet and using private connections is crucial for this use case.
TA
Tamala
1 year ago
Options B and E seem like the way to go. Connecting the SaaS service to a private endpoint and using a transit gateway to link the customer VPCs is a solid approach.
CE
Celestine
1 year ago
Agreed. It's important to maintain security and privacy while still allowing the necessary connections between the provider and customers.
ST
Stevie
1 year ago
That sounds like a good plan. Keeping the connections private and using a transit gateway for routing is a smart move.
VA
Valentin
1 year ago
E) Deploy an AWS Transit Gateway, and connect the SaaS VPC to it. Share the transit gateway with the customers. Configure routing on the transit gateway.
RO
Roxanne
1 year ago
B) Configure an endpoint service, and grant the customers permission to create a connection to the endpoint service.
BU
Buck
1 year ago
I think we should deploy the SaaS service endpoint behind a Network Load Balancer.