Closed CameronMcAuley closed 1 year ago
In addition, the README also tells the user to upload the template/dist to the following s3 location:
s3://$DIST_OUTPUT_BUCKET-$AWS_REGION/aws-waf-security-automations/$VERSION
If the user ran sudo ./build-s3-dist.sh $TEMPLATE_OUTPUT_BUCKET $DIST_OUTPUT_BUCKET $SOLUTION_NAME $VERSION
with a custom $SOLUTION_NAME, this is the directory within S3 that CloudFormation will look for.
If it doesn't find it, it will fail.
So, these AWSCLI S3 commands need to reference the $SOLUTION_NAME variable created earlier, i.e:
aws s3 cp ./deployment/global-s3-assets s3://$TEMPLATE_OUTPUT_BUCKET/$SOLUTION_NAME/$VERSION --recursive --acl bucket-owner-full-control
aws s3 cp ./deployment/regional-s3-assets s3://$DIST_OUTPUT_BUCKET-$AWS_REGION/$SOLUTION_NAME/$VERSION --recursive --acl bucket-owner-full-control
In general, this README needs to be much more verbose. I've wasted quite a few hours due to things that weren't clear.
Thanks for reporting the issue. We updated the readme in our most recent release to make it more clear. For example we give an explanation of each env variable and documented when to use each variable. However we do understand there are still confusions caused by missing details. We have added your request to our backlog so it will be addressed in future releases. We thank you for your contribution.
The readme instructions have been updated to provide more clarity. close the ticket.
Describe the issue
S3Bucket: !Join ['-', [!FindInMap ["SourceCode", "General", "SourceBucket"], !Ref 'AWS::Region']]
Changes Needed