You have the option to deploy Lumu Virtual Appliances as cloud collectors in cloud solutions such as AWS, Azure, and Google Cloud.
This guide contains the necessary steps to run a Virtual Appliance on Amazon Web Services Elastic Compute Cloud (AWS EC2) on a Virtual Private Cloud (VPC).
To ensure the successful deployment of a Lumu VA on AWS, you must meet the following minimum requirements:
Remember to confirm that inbound rules are set for allowing access to UDP port 53 for the VPC.
Once you have configured AWS and uploaded the Lumu Virtual Appliance, you are ready to activate and explore the VA general settings.
4. Consult our General Configuration guide for instructions on VA activation and setup.
After having your VA activated and configured, set the Lumu Virtual Appliance you created as the DNS name server.
5. On the AWS VPC console, go to the DHCP options set and create a new DHCP options set adding the Lumu Virtual Appliance you created as DNS name server. The DHCP is responsible for allocating IP addresses and other information to requesting clients.
6. Associate the new DHCP options set to your VPC by selecting the option to edit options set on the action list.
In the DHCP options set list, select the DHCP options set you created on step 5.
All the instances of the VPC will automatically pick up the changes within a few hours, depending on how frequently the instance renews its DHCP lease. You don't need to restart or relaunch the instances.
For the new DNS settings to take effect immediately on existing servers, you have the option to explicitly renew the lease being used on each server by the instance, see Flushing DNS Cache for guidance.
The final step is to verify that your DNS connections are correctly routed through Lumu. See Validate your DNS Settings for more information.