Must accepting Maketplace EULA or Palo Group creation will time out

[peterb154]

If you deploy the transit-vpc solution for the first time, without having ever deployed the Palo Alto virtual appliance in the TransitAccount, the cfts/paGroupCft.json will never create the EC2 instances and will time out and roll back, with no indication of why.

I finally figured out that it was because we had not ever deployed a Palo Image from the AWS Marketplace before in that Account and as such, had not accepted the Palo EULA. To correct this, I manually deployed a Palo instance in EC2, accepted the EULA then terminated that manual instance. From the on, paGroupCft.json worked.

I didn't see this in the documentation anywhere. Suggest that a note is added to the top of the deployment guide to provide assistance to others. Also suggest the deployment guide be in markdown (not pdf) so that the community might issue pull requests to improve the documentation.

Thanks!

[amico412]

Thanks for posting this, ran into the same issue.

[peterb154]

Thanks for posting this, ran into the same issue.

So glad it helped.