5 ms·
Great advice on technical implementation - thanks for this! I guess the takeaway I'm getting is that using this AWS-backed, encrypted tunnel will let me:
by OrwellianChild 9y ago
Great advice on technical implementation - thanks for this!
I guess the takeaway I'm getting is that using this AWS-backed, encrypted tunnel will let me:
Mask my traffic destination (via AWS routing)
Hide my traffic content (via encryption to AWS)
Minimize/eliminate tracking (assuming I don't accept cookies)
Are those the benefits I'm looking for out of this? Or am I missing benefits here?
- ktta 9y agoThe important part is knowing what you're looking for. Using a VPN isn't inherently going to make you more secure. It is advised to do so when you are in networks where you don't trust someone to not monitor your traffic or inject stuff into unsecured traffic. If you trust your ISP, then you really don't need a VPN. Unfortunately, most can't be trusted if you're in the US, especially since there was a recent senate action[1] that lets them collect and sell your history. If you do use a VPN, then the trust problems with ISP will shift towards trust in AWS. There's nothing stopping AWS from doing the same things that your ISP does. It is just that most people trust AWS to not do that. So to be clear, AWS can still see all your traffic and inject things into unsecured webpages. The VPN will just won't let your local ISP see what you're doing. All they see is encrypted traffic going to your AWS instance. Also your traffic is not anymore tracking proof when you use a VPN since instead of people storing your home IP address, they can store your AWS VPN's address (which no one really does anymore. They just use cookies and tracking elements). PS: Note that AWS charges for bandwidth. There are 'lightsail' instances where first 1TB egress is free. [1]: https://arstechnica.com/information-technology/2017/03/how-isps-can-sell-your-web-history-and-how-to-stop-them/ https://arstechnica.com/information-technology/2017/03/how-i...