With FH (FusionHub) running as a AWS VM, there remains a few hurdles for automated setup of a new FH instance.
- You are required to instantiate a new FH VM instance from a private AMI provided by PepWave. That is okay but you are still required to instantiate the VM, manually login though the FH management portal and specify 1) Timezone 2) Networking meta data including PepVPN configuration 3) FH license information.
In all cases, it is likely that an AWS ASG (auto-scaling group) would be used to ensure at least one AWS FH instance is running at all times. If the FH stops responding to an AWS health check (e.g. ping), then an ASG can be configured to terminate the stuck or missing VM and create a new VM.
It would be best if the meta-data listed above could be ‘passed’ to the VM instance creation via the USER DATA. User Data is used at VM start up to help configure things for unattended high availability. Creating an AMI image of a configured/running FH VM and using that custom AMI for VM instantiation does not work. Could be for any number of reasons but I’m guessing it is license related.
While I’m testing AWS FH with a evaluation license, I would expect this use case to come up in normal DevOps activities. Having to manually deactivate a FH license via the InControl2 website is going to be an obstacle under AWS.
Am I making sense here?