Browse through the questions and answers listed below or filter and sort to narrow down your results.
Problem Setting up EC2 as Airgap Server with Client VPN Endpoint
Afternoon All, I'm a (very) inexperienced user who's keen to learn and appreciate I might have bitten off far more than I can chew with this. I'm working on a project where we need to share UDP packets between two companies with the packets going in both directions. I want to setup an airgap server where exchange of data could take place. I have an EC2 server with an external IP address (that I SSH into) as the airgap machine and a VPN client endpoint linked to the subnet the EC2 instance is in. My intent was to send UDPs from my company system to the airgap on a particular port say 3005, for example and then listen on a different port, say 4005, for example, on the same EC2 instance for UDP packets from the other company. And use socat to send packets from 4005 to the client IP on my Windows machine (currently set in the Endpoint to 220.127.116.11/16 (yes I know the subnet is probably far too big for this)). I have successfully created the VPN client endpoint, downloaded the configuration file and can connect in from my Windows10 laptop using OpenVPN client. I can send packets from my Windows10 machine to the Airgap EC2 instance and see that it arrives on port 3005 as expected using tcpdump. I can also ping from the Windows machine to the Airgap server... so the connection is working in one direction. The issue I have is that the connection does not work sending packets from the Airgap EC2 instance to my machine via the VPN... If I run socat with various options of udp-recvfrom or udp-listen and udp-sendto or udp-datagram I get no packets arriving at my Windows machine. Neither can I ping the Windows machine from the EC2 Airgap instance (I have tried this with Windows Firewall turned off to test whether the FW was getting in the way) My questions then: 1. Is it possible to do what I want? 2. WHat am I doing wrong and how can I fix? 3. Is my assumption about an EC2 instance being a good way of setting up an airgap server like this correct? Many Thanks G
Client VPN Endpoint Authorization rules do not work as I intend to
I set Client VPN Endpoint ragarding this article. (https://aws.amazon.com/ko/blogs/security/authenticate-aws-client-vpn-users-with-aws-single-sign-on/) With just simple example of authorization rules, it does work well. But I added some rules more, it does not. Here is my examples. AWSSSO Group: - Group1 : can access all ip ranges in VPC (10.1.0.0/16) - Group2 : can access only Private Subnet 2 (10.1.255.192/27) VPC settings: - VPC: 10.1.0.0/16 - Private Subnet 1: 10.1.0.0/18 - Private Subnet 2: 10.1.255.192/27 - ... Authorization rules: 1. Destination network to enable access: 10.1.0.0/16, Grant access to: Allow access to users in a specific group, Access group ID: Group1 ID 2. Destination network to enable access: 10.1.255.192/27, Grant access to: Allow access to users in a specific group, Access group ID: Group2 ID With this configurations, Group2 can access to 10.1.255.192/27 well but Group1 can not access to 10.1.255.192/27(included in range of 10.1.0.0/16). I don't know why Group1 can not access to 10.1.255.192/27. Please tell me who knows why it happens.
AWS Fortigate S2S directionality issue...
I have an AWS to on-premise Fortigate site-to-site tunnel (static routing) configured and up. I could only pass traffic in the AWS-to-Fortigate direction after sending traffic in the Fortigate-to-AWS direction. Why is this? Is there a tunnel activity timeout involved?
How to fully uninstall aws client VPN
So I'm trying to use AWS VPN Client on my macOS Monterey version 12.4 Macbook Pro 16 inch 2019 When downloading a .ovpn from "Client VPN endpoints" I cannot seem to connect to the VPN. When I try to connect, I keep getting this from the client "Aws VPN Client is trying to install a new helper tool." in which it asks me for my credentials which I give it. Then immediately afterwards I get "AWS VPN Client Helper Tool is required to establish the connection." I've reinstalled the software about 8 times. Anytime I try to use the "Uninstall AWS VPN Client" I get "Uninstalled failed" with no additional information. So I manually delete the files, I run this command to do additional cleanup ``` sudo /bin/launchctl remove /Library/LaunchDaemons/com.amazonaws.acvc.helper.plist sudo rm /Library/LaunchDaemons/com.amazonaws.acvc.helper.plist sudo rm /Library/PrivilegedHelperTools/com.amazonaws.acvc.helper ``` I feel like im missing something obvious. It was working fine on my computer until recently. I've confirmed on another computer that the certs work fine. So if there is additional cleanup I can do, let me know. So I was wondering if this is a known issue or just me? I looked around and couldn't find any information in the FAQ or troubleshooting of it.
SFTP error from AWD VPC tunnel
We setup one site-to-site tunnel to a 3rd party vendor using our own fortigate firewall. The tunnel is up and running and we setup one Windows SFTP server in our network for the vendor to do file transfer. All credentials are shared to them but when they tried to send file to the server, they encountered "File Write error" ERROR Message: Error writing file 3: Permission denied. Firewall policies at both ends have already enabled all services to pass through. What could be the reasons why they cannot write to the SFTP server ?
AWS Site-to-Site VPN tunnel is available, put cant ping to ec2 instance
I spin up an EC2 instance in a public subnet on a /24. created a security group allowing SSH and ICMP from 0.0.0.0/0. Site-to-SIte VPN tunnel is up and running and using strongswan. However ping to the 169 address (inside tunnel) and to the ec2 instance does not work
Site-to-Site VPN with dynamic WAN address (LTE, Starlink, etc)
Heyo! I'm trying to create a Site-to-Site VPN between two sites without static WAN addresses. My backup plan is just to create the VPN server on an ec2 instance with a static external IP. The Client VPN Endpoints seem like a possibility but I don't think those will work since I have multiple networks I need to connect at each site and can't NAT through the endpoint. I'm looking at the documentation for Customer Gateways and seeing that specifying the external IP address is optional, so I'm hoping it may connect as a client if I don't specify that? If so I'm having some issues with the certificates that I'll need help with, but I should probably make a dedicated post for that. Is there another method for what I'm trying to do, or should I just spin up the EC2 instance and install my VPN server of choice and do this that way? Thanks so much for any help!
Site to Site VPN setup - Tunnel Status is Down
Hi There: I'm NOT able set up the Site to Site VPN, the Tunnel status is Always down. Any kind suggestion on this? Below is the steps what I have done to simulate On-Premise to AWS. Thanks. **I guess the Step4 might be the key reason? I'm trying to setup Static Routing**, but looks like we are ONLY allowed to create dynamic one? since the BGP ASN is required to be set? Months ago, the Custom Gateway front page is NOT like that, no BGP ASN required, but with selection: Static or Dynamic. **Attention here**: I'm trying to use **Static** Routing, NOT Dynamic. 1 - Created Two VPCs in one region naming VPC-AWS(10.100.0.0/16) and VPC-OnPremise(10.200.0.0/16) 2 - Created OnPremise-Public-Subnet(10.200.1.0/24, and auto assign public ip), Attached the subnet to Newly created Route(OnPremise-Public-Route), which added entry to IGW; Created AWS-Private-Subnet(10.100.1.0/24) 3 - Created Two Instances: OnPremise-Instance under OnPremise-Public-Subnet(automatically generated public ip - for example: 18.104.22.168), confirmed this instance can reach to anywhere; Created AWS-Instance under AWS-Private-Subnet (with Security Group allowed for all traffic: 0.0.0.0/0) 4 - Created Customer Gateway, with configuration below: 0) Name: CGW-OnPremise 1) BGP ASN: 65000 (I got confused this part, since monthes ago, there's no this section, but with ONLY to choose static or dynamic, and I was able to set up the site to site vpn connection without any problem that time, NOT sure whether this means we are ONLY allowed to setup Dynamic Routing? since I think BGP here means Dynamic routing - BUT I wants to setup Static one - Since so far I'm NOT familiar with Dynamic routing) 2) IP addressInfo: the public-ip of OnPremise-Instance above Above are the all configuration. 5 - Create VGW 0) Name: VGW-AWS 1) Autonomous System Number: Amazon default ASN 2) Attach it to VPC-AWS Above are the all configuration 6 - Create Site-to-Site VPN Connections 0) Name: S2S-VPN-Connection 1) Target gateway type: Virtual private gateway -> VGW-AWS 2) Customer gateway: Existing -> CGW-OnPremise 3) Routing options: Static -> (10.100.0.0/16, 10.200.0.0/16) Above are the all configurations for the configuration 7 - Go to the route table for AWS-Private-Subnet, Edit the Route Propogation to YES. 8 - Download the configuration from S2S-VPN-Connection(select OpenSwan), then Go to OnPremise-Instance, install OpenSwan, and configured properly, pasted one of the key part below: conn Tunnel1 authby=secret auto=start left=%defaultroute leftid=22.214.171.124 right=126.96.36.199 type=tunnel ikelifetime=8h keylife=1h phase2alg=aes128-sha1;modp1024 ike=aes128-sha1;modp1024 keyingtries=%forever keyexchange=ike leftsubnet=10.200.0.0/16 rightsubnet=10.100.0.0/16 dpddelay=10 dpdtimeout=30 dpdaction=restart_by_peer 9 - Then run: systemctl start ipsec And systemctl status ipsec, No errors, all look good. 10 - I think all set now, but I am NOT able to ping through the AWS-Instance(AWS side) from OnPremise-Instance(OnPremise side)
Important notice about your AWS Account regarding VPN connections
always received this email for the VPN issues , Hit was like the connection was dropped. We had setup 2 pair in each VPN Tunnel, is it still will drop? or this message is just a AWS notification email only? how to fix it ? " Your VPN Connection vpn-02cf818d35a89335d in the ap-southeast-1 Region had a momentary lapse of redundancy as one of two tunnel endpoints was replaced. Connectivity on the second tunnel was not affected during this time. Both tunnels are now operating normally. Replacements can occur for several reasons, including health, software upgrades, customer-initiated modifications, and when underlying hardware is retired. If you have configured your VPN Customer Gateway to use both tunnels, then your VPN Connection will have utilized the alternate tunnel during the replacement process. For more on tunnel endpoint replacements, please see our documentation . If you have not configured your VPN Customer Gateway to use both tunnels, then your VPN Connection may have been interrupted during the replacement. We encourage you to configure your router to use both tunnels. You can obtain the VPN Connection configuration recommendations for several types of VPN devices from the AWS Management Console . On the "Amazon VPC" tab, select "VPN Connections". Then highlight the VPN Connection and choose "Download Configuration"."
What are some of the strategies to handle Overlapping IP Ranges
What are some of the strategies to handle Overlapping IP Ranges for various integrations, within AWS as well as while planning hybrid connectivity with on-premises networks using VPN, DX etc. Note: This is a common question asked by AWS customers. Posting it to provide an answer that can benefit everyone.
AWS CLIENT VPN > Redshift private subnet DNS Resolution fails
Hello, I setup a AWS Client VPN, have some issues with DNS resolution for redshfit. there is no problems resolving to RDS which are in private subnet once im on VPN. Also i can connect directly to redshift if i use the private IP. But the problem i encountered is that Redshift DNS name doesnt resolve. the VPC does have the options enabled to resolve. Has any one encountered something similar?