Works only in us-east-1

[flochaz]

I tried to integrate this solution in an existing infrastructure deployed in eu-west-2 but due to the constraint around Lambda@Edge, deployment is failing (L@E should be deployed in us-east-1).

Would be great to have a proper handling of this case using something like https://github.com/yvele/aws-cfn-custom-resource-lambda-edge.

[mohsanjaffery]

This is a current limitation of the solution which will be addressed in an upcoming release. Thanks for pointing out that repo - we're looking at a similar approach.

[cailinw]

Is there any update on this? Would certainly be helpful to deploy this in a different region (e.g., us-west-2). Is there a way this can be modified to support this?
Thank you so much.

[mluthi69]

yeah, I'd like to deploy to ap-southeast-2

[assman]

Any updates on this? Would like to deploy it in ap-southeast-1

[mbk-ok]

Correct me if I'm wrong @mohsanjaffery, but could we make this extensible to non us-east-1 regions by simply making the Lambda layer CopyLayerVersion available in all other regions? That was the error I encountered when launching the stack in us-west-2.

[eidgenossen]

Could you not at least WARN people that this only works in us-east-1? Like mention it in the documentation? I've wasted a lot of time with this (I'm in eu-west-1)

[ConnorKirk]

So I've investigated this a bit further. It would be a nice feature to add, but I think the complexity cost might outweigh the benefits.

The current template is limited to the us-east-1 region because the AWS::ACM::Certificate resource needs to be located in us-east-1 to work with the CloudFront distribution.

I can think of two possible ways to create the ACM Certificate in us-east-1 regardless of deployment region:

1. Use a custom resource
2. Use Stacksets

Custom resource

Create a custom resource that creates the ACM Certificate in us-east-1 regardless of the deployed region of the template.

The downside of this is that it makes the template more complicated (more custom resources). It would also put the onus on either the custom resource or the user to validate the ACM certificate.

Stackset

Convert the AcmCertificateStack into a AWS::CloudFormation::Stackset resource. We can then specify it will always be deployed in us-east-1.

This has a few downsides:

• Might be surprising to users who aren't expecting resources to be created in us-east-1
• The AWS::CloudFormation::Stackset resource isn't yet supported by the aws cloudformation package command. Add AWS::CloudFormation::Stackset resource to the cloudformation package command aws/aws-cli#5590