Regarding the magic in git-lfs.yaml

[alanedwardes]

Regarding the magic in git-lfs.yaml

[alanedwardes]

Hi,

When I try this, CloudFormation complains about the code bucket being in a different region:

Error occurred while GetObject. S3 Error Code: AuthorizationHeaderMalformed. S3 Error Message: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'eu-west-1' (Service: AWSLambda; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 53249a0d-c2a5-11e8-8673-e93cc8a11d3f)

Did you change this and see it working?

Cheers

[jdannenbring]

I hadn't tried it till now. Looks like the issue is my lambda function on us-west cannot access your 'ae-infrastructure-eu-west-1' bucket (even though its publicly downloadable).

When I make a bucket and put the git-lfs-lambda.zip there, then the code in the yaml works:
Code: S3Bucket: !Sub 'cf-templates-124hcfrvf3ol2-${AWS::Region}' S3Key: git-lfs-lambda.zip

Where cf-templates-124hcfrvf3ol2 was my bucket name.

[alanedwardes]

No - this is a limitation of AWS Lambda. Since I don't want to maintain a bucket in each region, the script will only support eu-west-1 for now - so hardcoding that region or keeping it as ${AWS::Region} is functionally the same :)

[jdannenbring]

I see, understood. Thanks!