@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. <pulse-config><admin-password>redacted</admin-password><admin-username>pcsadmin</admin-username><wins-server>18.104.22.168</wins-server><dns-domain>psecure.net</dns-domain><cert-common-name>va1.psecure.net</cert-common-name><cert-random-text>fdsfpisonvsfnms</cert-random-text><cert-organisation>Psecure Org</cert-organisation><config-download-url></config-download-url><config-data></config-data><auth-code-license></auth-code-license><enable-license-server>n</enable-license-server><accept-license-agreement>y</accept-license-agreement><enable-rest>n</enable-rest></pulse-config> 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
... View more
Hello, 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.
... View more