Do I need NAT translations for IP addresses when I use AWS?

Asked 2 years ago, Updated 2 years ago, 43 views

We will use EC2 in AWS to build one server.
Access to office servers for business interaction and maintenance from several clients.
AWS and the office will be connected via Internet VPN.

It was stated on the net that it is recommended that the IP addresses assigned to EC2 servers should be assigned to those that do not cover the IPs used on-play.

In this environment, is the IP assigned to the server on AWS a private IP?
Or is it global IP?

Or will both the AWS side and the office side have a private IP and a global IP for communication over the VPN?
If so, do I need NAT translations?

I'm a beginner around the network and I don't know how to think about using the cloud in general, so I asked you a question.

aws

2022-09-30 17:04

1 Answers

Assume that the Internet VPN is a site-to-site VPN (site-to-site VPN).

The IP address should look like this:

< u l >
  • servers on AWS:private IP addresses
  • Office servers:private IP addresses
  • Office VPN router: Public IP address *Register on AWS as Customer Gateway
  • NAT translation should not be required if the CIDR is not duplicated between AWS and the office.
    (If NAT translation is required, I feel that there was no managed service, so I think you need to do your best.You might find it helpful to VPN-configuring NAT for traffic or something like that.)

    With the site-to-site VPN with AWS, I think the following pages are easy to understand.
    Tried VPN connection between home and AWS|DevelopersIO
    Tried VPNing Home to AWS (Cisco Router Edition) | DevelopersIO

    *By the way, I heard that Client VPN is now available (I'm not sure, but this may be better depending on the purpose).
    [AWS] Get rid of your stepping stone!?Try Client VPN for VPC connections | DevelopersIO


    2022-09-30 17:04

    If you have any answers or tips


    © 2024 OneMinuteCode. All rights reserved.