4 ms·
I think in a lot of cases folks still make certain things public instead of using a VPC out of convenience. For example if a developer needs to access a resour
by nickjj 5y ago
I think in a lot of cases folks still make certain things public instead of using a VPC out of convenience.
For example if a developer needs to access a resource within a VPC then this sky rockets complexity. You can't just connect to something running in a VPC from the outside world. You'd have to install and configure a VPN and it becomes a whole ceremony for both the person setting all of this up and the person connecting.
Using a VPC/VPN and keeping your important things internal (like a database or staging environment, etc.) is a really good idea but unless you have someone who has a really solid understanding of this it's a whole lot easier to make something public, restrict a security group by IP and keep a whitelist of IPs up to date for developer access.
- wbkang 5y agoHow about just setting up a bastion host and then forwarding ports via SSH? It's much simpler than setting up a VPN.