Dear support team,
Our organization recently acquired an Enterprise subscription, and I have been exploring options for deploying Pritunl, particularly focusing on its integration with AWS Auto Scaling Groups (ASG). During this process, I encountered some challenges and observations that I would like to address:
-
Setup Key Requirement: Each time a Pritunl server instance is initiated, it prompts for a setup key in the user interface to activate the server. This manual step poses a challenge to automating the deployment process within an auto-scaling environment.
-
AMI-Based Deployment Observations:
2.1 After creating an Amazon Machine Image (AMI) from a configured Pritunl server and deploying a new instance using this AMI, I observed that the setup key was not required upon first accessing the UI, which was expected.
2.2 The new instance did not register as a distinct host; instead, it appeared identical to the original instance.
2.3 Both the original and new instances operated concurrently without recognition of each other as separate entities.
2.4 Notably, the only change was that the private IP address in the database updated to reflect the new instance’s IP.
Given these observations, I seek clarification on the following points:
-
Expected Behavior: Is it standard for Pritunl instances cloned from an AMI to not recognize each other as separate hosts, and for the private IP address in the database to update accordingly?
-
Automated Deployment in ASG: Is there a recommended approach to deploy Pritunl within an AWS Auto Scaling Group without manual intervention, such as entering the setup key? Specifically, are there best practices or automation strategies to facilitate seamless scaling of Pritunl servers in this environment?
I appreciate any guidance or resources you can provide to assist in achieving an automated and scalable Pritunl deployment on AWS.
Thank you for your support!