Simplify your developer workflow and work faster

Developer Workflow

92% of enterprises have a multi-cloud strategy; 80% have a hybrid cloud strategy.  Hybrid and multi-cloud support the best of breed, increase agility, and improve the bottom line. Developers need to connect to multiple locations at once. Today's modern continuous integration (CI) and continuous development (CD) pipeline includes source code control, build and test automation, release automation, and finally a deployment stage.

The same is true for DevOps and IT teams that need to manage development, test, and production environments as well as devices scattered around the world.

VPNs were created over twenty years ago to connect remote workers to an organization's data center. Since then, cloud applications, BYOD, and a prominent work from home environment have changed the world. Users access resources using devices, networks, and software that the IT team has no control over and is likely unaware of.

Today's developer is on the move working from home, the company office, shared workspace, or an Airbnb.  VPNs create the following issues:

• VPNs are not always on and developers need to add one extra step to the login process.
• Due to IP routing limitations with VPNs, developers can't connect to two VPNs at the same time to avoid subnet collisions.
• VPNs route all traffic through a centralized location/server so scaling VPN hardware is a burden.  It's either expensive with hosted solutions or time-consuming and a possible security vector for having unpatched VPN services and agents.
• Developers have to talk to IT or DevOps to add IP addresses to the Access Control List.  Alternatively, some organizations allow developers to update the Allowed/Whitelist on their own which reduces the number of employees in the process but could lead to security threats.
• VPNs can be set up in a “split-tunnel” where private IP addresses route through the VPN but public IP addresses route through your own internet connection.  This means that your public IP address changes when you are at a coffee shop even when on a VPN.  It is also a false sense of security because you believe you are using the VPN 100% when in fact you are not.
• Some MySQL databases only have a public endpoint such as an AWS RDS MySQL setup for public access.  VPNs can't solve this problem.
• If you need to grant public access to some users, you will still need to have an access list. Now you are managing a VPN and an Access List.

How do developers access AWS resources using Remote.It

Remote.It will map network connections such as AWS cloud services to a local address for developers to use. Here are some examples.

Secure Shell (SSH)

Connect directly via command line to any service or server

Database

Connect to databases such as Redis, RDS or DynamoDB

HTTPS/HTTP

Connect to web applications

Remote Desktop

Remote desktop into servers such as Windows EC2 instances

‍