You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 2, 2021. It is now read-only.
Error while creating cloudformation stack : waf-reactive-blacklist . Lambda function creation is failing as it is unable to find key in bucket "heitorc".
#21
Open
ppm-vinay opened this issue
May 16, 2017
· 4 comments
Following code is creating problem in waf-reactive-blacklist:
"Code": {
"S3Bucket": {"Fn::Join": [".", [{ "Ref" : "AWS::Region" },"heitorc"]]},
"S3Key": "waf-reactive-blacklist/parser.zip"
},
The above code in cloudformation results in BucketNotFound error while I tested with python api and was able to fetch file.
FYI; I got a permission denied for the above (using us-east-1). Ended up just downloading waf-reactive-blacklist/parser.zip from this repo, uploading it to one of my own buckets and then updating the template with the new location.
updated: just need to edit template.json line 264 to "Code": {
"S3Bucket": "yourbucketname",
"S3Key": "waf-reactive-blacklist/parser.zip"
},
@jmilliron which part in the template you update to have your own bucket location? i tried changing the key for "S3Bucket" but it's still failing with below error.
error occurred while GetObject. S3 Error Code: NoSuchBucket. S3 Error Message: The specified bucket does not exist
i copied the waf-reactive-blacklist/parser.zip to my s3 bucket and updated the template . It worked
"Code": {
"S3Bucket":"bucketname",
"S3Key": "key to zip file"
}
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Following code is creating problem in waf-reactive-blacklist:
"Code": {
"S3Bucket": {"Fn::Join": [".", [{ "Ref" : "AWS::Region" },"heitorc"]]},
"S3Key": "waf-reactive-blacklist/parser.zip"
},
The above code in cloudformation results in BucketNotFound error while I tested with python api and was able to fetch file.
So the bucket name formed is somehow wrong in cloudformation and needs to be updated correctly.
The text was updated successfully, but these errors were encountered: