remote.it for AWS is a one-stop zero-trust solution for managing access to your AWS VPCs, instantly freeing you from legacy methods of access, including open ports and access control management using an IP whitelists.
- Email based access
Set trusted access by “who” instead of “where” by using email addresses (OAuth) to manage access. With remote work and distributed workforces, IP whitelists are no longer a practical means of permitting access.
- Trusted access from any network location
Access your VPCs and VPC services from any location eliminating the manual and error-prone practice of whitelisting IP addresses for your employees.
- Restrict access to AWS services and resources
Instead of needing to provide full VPC access and managing secondary authentication rules, admins can decide who has access down to the individual AWS service or resource.
- Locked down security groups
Exactly what you’d demand from a zero-trust solution, remote.it for AWS requires zero inbound ports.
- Zero attack surface
Never worry again about exposed inbound ports. Make new or existing VPC deployments undiscoverable by hackers, eliminating the risk of DDoS or malicious attacks and services breaches, without any changes to your existing VPC infrastructure or networking.
The Radical, Yet No-Brainer, Principles That Led Us
to Build remote.it for AWS
Focus on users,
not network location
The secure and trusted remote access model needs to shift from “where computers are located” to “who needs access.” Where a worker is no longer important in a remote-first world.
Provide access to only the people who need it
IP whitelisting is not as secure as commonly assumed. For example, a whitelisted developer on a mobile network hotspot with a CGNAT address, or at co-working space, essentially permits any connection from that network to see the IP address
Change from open access to
Open port usage is downright crazy.
Historically, IP addresses and open ports were designed to solve building-to- building connectivity with firewalls at both ends, not distributed, remote users.
remote.it for AWS: Cloud Access Re-Imagined
The Trusted Remote Access Solution for VPCs
Make new or existing VPC deployments undiscoverable by hackers, eliminating the risk of DDoS or malicious attacks and VPC services breaches: no changes to your VPC infrastructure or networking.
Access your VPCs and VPC services from any location eliminating the manual and error-prone practice of whitelisting IP addresses for your remote developers and engineers.
Achieve VPC compliance with ease: Provide an auto-maintained access log for auditing
- AWS Service and resource-level restriction: No need to grant full VPC access and manage complex secondary authentication rules. Simply assign user access to specific services and resources within a VPC.
- Works with all popular AWS resources and services: If it typically uses a port for access, it will work with remote.it. Without opening ports or managing IP whitelists, easily provide trusted access to REDIS, RDP, SSH, OpenVPN, AWS private links, and more.
- One stop, zero-trust solution for your AWS VPCs: Access VPCs, services, and resources from any location, while closing inbound ports to the Internet that can be exploited by bad actors.
- Easy to use: A DevOps manager can use remote.it to share access to an AWS instance or service. The user can then access the instance any time using remote.it and their email address.
- Secure connections: remote.it validates that the user has permission to access, then sends a unique key to both the user and AWS that is used to make a secure tunnel between the user and the AWS instance/resource.
- Works with or without VPN: An encrypted peer to peer tunnel is established between the user and the private AWS instance: no inbound ports, no IP restriction rules needed.
- Keep existing tools and software: remote.it uses localhost:port to access the private AWS instance/resource maintaining compatibility with applications and APIs developers use to get access to a production Redis or other service and instance.
- Audits: All access is logged in the admin’s remote.it account and the admin can revoke access or close connections to a user’s email at any time.