This change is necessary to fix the problem that I was experiecing: 503 in CloudFront, because the Lambda@Edge doesn't have privileges to access the bucket created by stack-proxy instances.
The proposed solution is sub-optimal, I think that a better solution is the ${DefaultBucket} be used by all stack-proxy instances. But, for the sake of this lab, I think that it is an interesting solution.
This change is necessary to fix the problem that I was experiecing: 503 in CloudFront, because the Lambda@Edge doesn't have privileges to access the bucket created by stack-proxy instances.
The proposed solution is sub-optimal, I think that a better solution is the ${DefaultBucket} be used by all stack-proxy instances. But, for the sake of this lab, I think that it is an interesting solution.