PA-Groups are exausted even though no VPNs have been configured about aws-transit-vpc HOT 4 CLOSED

Update on this from my side, problem solved.

I solved this issue by deleting all stacks including the transit VPC stack (initializeTransitAccount.json) and then running them once more.

I believe that the issue was that I had a bunch of failed attempts to run the initializeSubscriberAccount.json due to some configerrors caused by not having approved the software terms for the Palo VMs before running the script (could not find any info of this being needed in the guides for this setup, but for example Cisco have this documented: https://docs.aws.amazon.com/solutions/latest/cisco-based-transit-vpc/step1.html ). The failed attempts to create the Subscriber setup seems to have added some info to the DynamoDBs for the transit VPC that was not cleaned when the stacks for the failed Subscribers where deleted.

Hopefully this will help someone else in the future!

/J

from aws-transit-vpc.

Hi Mr.Lehto I'm having the same issue and already tried to deleted everything and try again but it didn't work for me.

I'm doing this on a brand new account, do you think there's any limitations to that that might be conflicting?

from aws-transit-vpc.

from aws-transit-vpc.

Follow the instructions to accept the market place terms and conditions. In order to do this just go through the steps to deploy a firewall from the marketplace. You will be prompted to accept the terms and conditions.
…
On Wed, 24 Apr 2019 at 04:12, Simbec @.***> wrote: Hi Mr.Lehto I'm having the same issue and already tried to deleted everything and try again but it didn't work for me. I'm doing this on a brand new account, do you think there's any limitations to that that might be conflicting? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#45 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEAEZXCLT7QE2FMWLEXB62TPR7F3JANCNFSM4FUUQHGQ .

Hi, jharris. Thanks for your reply, I really appreciate it. We already accepted the terms and conditions, the PaGroups deploy just fine and they even bootstrap correctly. We followed that instruction even before deploying the stack still got the PaGroup exhausted issue.

Thanks.

from aws-transit-vpc.