Deploying solutions based on standardized, readily available hardware has dramatically simplified the development of distributed and IoT solutions. Virtual devices can now be deployed instantaneously in cloud platforms such as Amazon Web Services (AWS) and Arm Virtual Hardware (AVH). Developers can host various solutions on Raspberry Pis and other standardized hardware platforms, including productivity, entertainment, and communication solutions.
‍

Local is easy

Local development is straightforward. Access the Raspberry Pi IP address from another device on the same LAN (Local Area Network). Developers use their favorite tools, including SSH (Secure Shell), VNC (Virtual Network Computing), and web browsers.

Challenges of remote development

Remote development adds more steps and creates security risks. You need public IP addresses and open ports to connect remotely. There may be a VPN (Virtual Private Network) to set up, or firewall rules and IP allow lists to manage. Remote development is possible. It requires extra work and leaves the public IP address and port accessible by malicious actors and bots exploiting known CVEs (Common Vulnerabilities and Exposures) and day 0 threats.

Developing remotely in a third-party cloud is similar to any remote development with further restrictions on what tools and admin rights users are granted.  
‍

Arm Virtual Hardware

‍
Arm Virtual Hardware (AVH) to the rescue. AVH is a public cloud offering similar to AWS, providing access to a virtual device like a Raspberry Pi. Just like spinning up an EC2 instance in AWS whenever you need, you can now create virtual Pis or other Arm-based development environments whenever you want.

It’s simple to set up a virtual device with Remote.It  

AVH provides a web portal to create and manage all your virtual devices. Within that web portal, you can also directly SSH into your virtual device. You don’t need to know the IP address of the virtual device, set up port forwarding, route tables, security groups, etc. Effortless to access the console of your virtual device.

What if you need more than SSH access to your device, such as access to databases, web applications, VNC, file transfers, and more? Or what if services in other clouds need to connect to the AVH device?  

Remote.It Solution

Remote.It to the rescue. Remote.It provides simple and secure remote connectivity to public and private clouds, on-premise devices, IoT, and more without managing or understanding networking. With Remote.It, developers can:  

• Eliminate the hassle of managing IP allow lists.
• Eliminate subnet range overlaps
• Eliminate VLAN segregation
• Eliminate docker, AWS/public cloud routing tables
  ‍

Remote.It simplifies connectivity to devices, including your Arm AVH virtual devices. All remote devices appear local to the developer. Developers continue using their existing tools and local IP address or host names.

Besides being the simplest remote connectivity solution, Remote.It is also the most secure. Remote.It doesn’t require a global public IP address or exposed port for remote devices. Devices are invisible from the public Internet. It eliminates the external attack surface of bots and malicious actors scanning your IP address and ports for known vulnerabilities or services with weak passwords.

Unlike traditional VPN solutions that grant users access to an entire subnet, Remote.It grants access at a service level. Imagine a device hosting a web application, a MySQL database, and an SSH service. A traditional VPN would only be able to grant access to the subnet/device. An authorized user would have access to all three services. With Remote.It, users can be given access at the service level. IT admins could have SSH access without access to the web application or database. The database admin may have access to just the database. At the same time, application developers may access only the web application and the database. Deploying micro-segmentation or least privileged access is a core requirement of Zero Trust.

There is a more straightforward and more secure way to develop remotely. Use Remote.It 

Benefits of Remote.It with AVH

Unified & automated network management

• Automate network configuration. Eliminate person-hours spent planning, maintaining, and resolving IP address, subnet, routing table, and VLAN configurations.
• A single dashboard consolidates users, services, and devices into one management dashboard. Devices can be on-premise or in the cloud, such as AVH.

Zero Trust security

• Least privileged access. Unlike a traditional VPN, grant access controls to services without exposing the entire subnet. Allow users to access your web application without having access to SSH, for example.
• Eliminate external attack surface. Keep private resources off the public Internet. There is no need for a global IP address or port forwarding. Bots and malicious actors scan global IP addresses over 50k times daily, looking for known vulnerabilities or services with weak passwords.

Immediate ROI

• The basic Remote.It account is free forever.
• Immediately save time by eliminating managing IP allow lists, subnet range overlaps, VLAN segregation, and Docker/public cloud routing tables.
• Eliminate expensive VPN licenses and hardware.
  

How to get started with Remote.It

Start with Remote.It for free. Remote.It has plans for everyone, including free forever plans and paid plans, including organization management and SSO (Single Sign-On) integration.  

• Getting Started with Arm Virtual Hardware Raspberry Pi 
  

Arm AVH device deployment has Remote.It installation as a pre-built option. Click the Install Remote.It option from within the AVH console when creating and deploying your virtual device.

Summary

Remote.It provides a simple solution to remotely access your virtual Arm devices hosted in Arm Virtual Hardware. Remotely access any service hosted on your virtual device.

• Supports web applications, SSH, RDP, databases such as MySQL, VNC, file transfer, games, and more
• No VPN required
• All virtual services appear local to the remote user
• No router or firewall network configuration changes required
• Collaborate and share services via an email address
• Groups of virtual devices can be put into logical ‘networks’ for ease of management
• Devices can belong to multiple networks at the same time
• Users can access devices in AWS, GPC, Azure, on-premise, and Arm AVH at the same time
• Devices can be pre-provisioned with tags for virtual machine and container environments

‍