[…] I set up a cloud service where my VPN service would be located on Amazon’s web services, a reputable and widely trusted cloud provider. […] After about an hour, I set up a VPN that worked flawlessly. The best part? Not only is it free to use […]
Sorry, what? Last time I checked AWS VPSs were very much NOT free to use, and I’m pretty sure the lowest tier is still more expensive than your average VPN.
Also, this article seems to be arguing against its own points: “you probably don’t need a VPN, but I have one anyway”…
It has a free tier, for 12 months you can run one t3.micro for free. That’s more than enough for a single user VPN. Afterwards it costs like $9 a month for on-demand instances (in the EU, it’s cheaper in the US), at that point you can either switch to reserved instances (which brings the cost down to around $3 or create a new AWS account to enjoy the free tier again.
Sorry, what? Last time I checked AWS VPSs were very much NOT free to use, and I’m pretty sure the lowest tier is still more expensive than your average VPN.
Also, this article seems to be arguing against its own points: “you probably don’t need a VPN, but I have one anyway”…
It has a free tier, for 12 months you can run one t3.micro for free. That’s more than enough for a single user VPN. Afterwards it costs like $9 a month for on-demand instances (in the EU, it’s cheaper in the US), at that point you can either switch to reserved instances (which brings the cost down to around $3 or create a new AWS account to enjoy the free tier again.
My guess is they’re using an AWS free tier VM to host a VPN. It’s not a bad option but it can be insecure unless you know what you’re doing