setup a FREE VPN server in the cloud (AWS)

A free, self-hosted VPN is achievable by running OpenVPN Access Server on an AWS EC2 instance using the AWS Marketplace “free tier eligible” option—then routing all client traffic through the tunnel for encrypted browsing. The practical payoff is simple: anyone can connect a laptop, phone, or other device to a cloud-based VPN, mask their public IP, and securely access private AWS resources without paying for a commercial VPN subscription.

The setup starts in AWS with an EC2 “launch instance.” Instead of installing OpenVPN from scratch, the workflow uses AWS Marketplace to find an Ubuntu server image that already includes OpenVPN Access Server. The key selection is the “free tier eligible” variant, which avoids ongoing software licensing costs for basic use. While OpenVPN itself is free and open source, OpenVPN Access Server is commercial; this particular Marketplace image is configured as a “bring your own license” style that allows two free client connections—enough for a user and a friend. After choosing a free-tier instance size (t2.micro), the only other required AWS artifact is an SSH key pair. The key must be downloaded immediately because it’s the only chance to retrieve it later.

Once the EC2 instance is running, the next step is connecting via SSH and initializing the OpenVPN Access Server. The process involves accepting prompts, switching from root to the openvpn user, and setting an admin/client password using a command that updates the openvpn user’s credentials. After that, the admin interface is reached through the instance’s public IPv4 address on port 943, using the /admin path. Logging in with the openvpn username and the password created during initialization unlocks the configuration.

The crucial security change happens in the admin panel under routing: enabling “all client traffic should be routed through the VPN.” Saving settings and applying the update ensures that connected devices send their internet traffic through the VPN tunnel, not directly to the public internet. With the server configured, clients use the user portal (same IP, port 943, but without /admin) to download the appropriate OpenVPN client for their device.

A Windows client install is shown as an example, but the same portal supports other platforms like iOS and Android via an app. After installing and signing in with the same openvpn credentials, connecting should shift browsing traffic through the VPN. Verification is done by checking “what’s my IP” in a browser; the public IP should change to match the AWS VPN server rather than the user’s home ISP.

Finally, the cost logic is grounded in AWS Free Tier rules: a free-tier account provides 12 months of access, and a single t2.micro instance can run up to 750 hours per month for free (744 hours is roughly a month). After the free period, the instance cost is estimated around $10/month, still positioned as competitive with many paid VPN services. The result is a cloud-based VPN that can also support secure access to AWS private networks (VPC) while keeping traffic encrypted and private.