.png)
Installation in Private Cloud
As an alternative to using on-premises servers, the MyQ Server can be installed and run on an Azure Virtual Machine, with a VPN tunnel connecting the physical network and Azure's virtual network, or using site-to-site VPN via Amazon Web Service (AWS).
Private Cloud Using Azure
Environment Requirements:
The minimum recommended virtual machine is B4ms, with a dedicated (non system disk) standard HDD.
The recommended CPU, RAM and HDD resources are the same as a standard installation and can be found in system requirements.
VPN tunnel (100mbps line is recommended) connecting the physical network and Azure's virtual network where the MyQ Server is installed.
Outgoing communication on ports used by MyQ must be allowed on Azure's Network security group. See main communication ports for a full list.
The geolocation of the cloud server should be as physically close as possible.
The Ping answer from printers to the cloud server should be within 750 ms (max 1 second, can be adjusted in config.ini)
For more information about Azure - Extend an on-premises network using VPN, see:
Once you set up the Azure virtual environment, follow the Installation instructions to install MyQ.
About MyQ in Private Cloud
Customers using Microsoft 365 as a private cloud hosting their internal systems can add MyQ to the list of IT services they no longer need to have installed on an on-premises server.
Part of the leased private cloud space can be dedicated to MyQ server(s), and MyQ running in Azure can make use of Azure Active Directories.
The single sign-on feature already used by users to access applications in the Microsoft cloud can also cover cloud printing with MyQ, without the need to use a VPN connection.
MS Universal Print is also fully integrated in MyQ, offering mobility, quick printer discovery, and no need for a VPN connection.
What is more, MyQ’s Universal Print connector can work with older devices, so there’s no need to invest in upgrading your fleet with more recent models which would natively support Universal Print.
A VPN tunnel connecting the physical network and Azure's virtual network is also required when using Microsoft Universal Print. Thanks to this VPN tunnel, there is no need for a VPN connection from the client’s side to the MyQ Server.
Private Cloud Using Amazon
Environment Requirements
Amazon EC2 Instance: MyQ Server(s) can be installed on an AWS EC2 instance. The instance should meet the standard system requirements for MyQ X installations, which include sufficient CPU, RAM, and storage. Refer to the MyQ X Documentation for detailed system requirements.
AWS VPC Setup: Create an AWS Virtual Private Cloud (VPC) with necessary resources like subnets, route tables, and gateways. Follow the procedure outlined in the AWS VPC guide.
Site-to-Site VPN: A site-to-site VPN tunnel is mandatory to connect your on-premises network with the AWS VPC. This VPN allows MyQ X to access resources on the local network. The setup process involves creating a customer gateway, a virtual private gateway, and configuring routing and security groups on AWS. Detailed steps can be found in the AWS Site-to-Site VPN documentation.
When connecting your AWS VPC to your on-premises network via a site-to-site VPN connection it is assumed that the target on-premises network has resources like a DNS server, a DHCP server, a network switch, or router, an internet gateway, a physical or virtual firewall, etc. Other resources like a domain, a domain controller, a file server, an SMTP server, etc. are optional.
Getting started with AWS Site-to-site VPN
For details, refer to the AWS guide.
Create a Customer Gateway: Represent your on-premises network’s VPN device in AWS. This involves entering the static IP address of the device and selecting appropriate routing options. Follow the steps in the AWS Customer Gateway guide.
Create a Virtual Private Gateway: This is the VPN gateway on the AWS side. After creation, attach it to your VPC. Instructions are detailed in the AWS Virtual Private Gateway guide.
Configure Routing: Update your VPC’s route table to direct traffic through the VPN connection to your on-premises network. Refer to the AWS Route Table Configuration.
Update Security Groups: Modify the security group associated with your EC2 instance to allow necessary inbound and outbound traffic. See the AWS Security Group guide for details.
Create the VPN Connection: Establish the VPN connection between your AWS VPC and your on-premises network by configuring the necessary tunnels. Detailed instructions can be found here.
Download Configuration File: Download the configuration file provided by AWS to set up your customer gateway device.
Configure Your Customer Gateway Device: Follow the instructions in the configuration file to complete the VPN setup on your on-premises gateway device.