Open PerryKuhnen opened 6 years ago
Agreed. Will forward it to dev team t open and fix bug
So it turns out it is not a bug. I should have figured that out...but if you don't change the bucket name we will use the default bucket and append the region where you have deployed the template. If you use your own bucket, the template will just use that name. You have to make sure that the bucket you use is in the region where are deploying the template.
In the firewall-v2.0.template file there is a mapping for the default region of the S3 buckets. The default values are not regions but the value panw-aws-autoscale-v20 This is the default name of the bucket not the region. This value should default to something like us-east-1 otherwise this template doesn't work and the lambda functions won't get called. I've tested this and as soon as I changed the value to us-east-1 where my S3 buckets are it started working. I'm testing thi v2.0 template as a nested stack and passing in parameters to set these.