Has anyone successfully deployed Pulse Connect Secure - BYOL 3 NIC or Pulse Connect Secure - BYOL 3 NIC in AWS GovCloud? Precisely us-gov-east-1. The AMIs provided by Pulse Secure (after subscribing) are unable to parse the userdata. That same userdata works perfectly on PCS AMIs in us-east-1/us-east-2. Hence, the server is unable to completely boot up due to the license agreement not being automatically accepted.
@mayowa - were you able to raise a support ticket for this?
I have asked the team to look at this - the PCS virtual appliance should work correctly in us-gov-west, so this problem may be limited to us-gov-east.
Can you check us-gov-west?
@pwallace I didn't raise a ticket yet. I just tried deploying to us-gov-west using ami-ee0e328f and I'm seeing the same behavior. Below is the userdata I'm using.
Here's the log from the console:
Starting Core Services This is AWS environment; checking if user-data is available Initial configuration file not present or unable to parse configuration data
Can you confirm which instance type you are attempting to use on us-gov-west?
I think you will need to raise a formal ticket so our team can look at the details on this one