Answers: <p>A possible approach could be:</p>
  <ul>
  <li>Put your instances in a private subnet</li>
  <li>Route incoming traffic through a load balancer</li>
  <li>Route outgoing traffic through a <a href="https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html" rel="nofollow noreferrer">NAT</a></li>
  </ul>
  <p>Outgoing traffic will then use the elastic IP assigned to your NAT as its source IP.</p>
  <p>An added benefit of this approach from a security perspective is that your instances won't be directly reachable from the internet, thus reducing your attack surface.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-05-19T11:56:53.310Z
Answers: 2020-12-19T17:17:00.883Z
Answers: 2020-12-19T17:17:00.883Z
Answers: Lykanion
Body: <p>Currently we are running an application in a single amazon ec2 machine. On our application we are using some third party solution. For using those solution, we have asked the third party service provider to whitelist our ec2 machine ip.</p>
  
  <pre><code>our EC2 machine: IP - 172.12.32.55
  Third party solution like global.bank.com and we have told global.bank.com to whitelist our IP
  </code></pre>
  
  <p>Now we want to scale up our application. We are planing to setup multiple node (our application in multiple ec2 machine) and a load balancer.</p>
  
  <p>So my questions is, how i can manage our third party solution provider? Should I give all our ec2 machine ips to our third party solution providers for whitelist? Or is their any other solution to handle the situation?</p>
  
Tags: <amazon-web-services><amazon-ec2>
Title: amazon ec2 ip whitelisted on a third party service provider
UserDisplayName: Hasan Hafiz Pasha
ThreadText: # amazon ec2 ip whitelisted on a third party service provider
  
  (Asked by: username_0 on 2020-05-19)
  
  Currently we are running an application in a single amazon ec2 machine. On our application we are using some third party solution. For using those solution, we have asked the third party service provider to whitelist our ec2 machine ip.
  
  ```
  our EC2 machine: IP - 172.12.32.55
  Third party solution like global.bank.com and we have told global.bank.com to whitelist our IP
  
  ```
  
  Now we want to scale up our application. We are planing to setup multiple node (our application in multiple ec2 machine) and a load balancer.
  
  So my questions is, how i can manage our third party solution provider? Should I give all our ec2 machine ips to our third party solution providers for whitelist? Or is their any other solution to handle the situation?
  
  **Tags:** amazon-web-services, amazon-ec2
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-05-19. Score: 3 | Accepted answer
  
  A possible approach could be:
  
  * Put your instances in a private subnet
  * Route incoming traffic through a load balancer
  * Route outgoing traffic through a [NAT](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html)
  
  Outgoing traffic will then use the elastic IP assigned to your NAT as its source IP.
  
  An added benefit of this approach from a security perspective is that your instances won't be directly reachable from the internet, thus reducing your attack surface.
  
  
  ---
  
  