Template self host

[craigjbass]

I've noticed that the available regions is quite a small list, is there a way that we can get around that by referencing a template that we put somewhere ourselves?

The only other tool I can think of is AWS Copilot, which does a similar job of creating CloudFormation Templates, but that doesn't require referencing a template that is only available in a specific region - it's all generated locally.

In our use case we want to use eu-west-2

[jdstuart]

I have a similar problem. We'd like to try this out in the ca-central-1 region.

[olkitu]

This could be small issue so I would recommend maintainers reserve all Bucket names with granted-releases-<AWS_REGION> because currently anyone can create bucket and possible host malware content in. If not like host every possible region then I would recommend allow custom Template Self-Host path set to gdeploy tool. This is POC i have tested to work:

Set version as environment variable

export GLIDE_VERSION=v0.12.0

Create S3 Bucket to region not officially supported

aws s3 mb s3://granted-releases-eu-west-1

Download from us-east-1 locally

aws s3 sync s3://granted-releases-us-east-1/$GLIDE_VERSION $GLIDE_VERSION

Replace Lambda S3 bucket name because must be in same region as Lambda function

sed -i 's/granted-releases-us-east-1/granted-releases-eu-west-1/g' $GLIDE_VERSION/Granted.template.json

Sync files to your own S3 bucket

aws s3 sync $GLIDE_VERSION s3://granted-releases-eu-west-1/$GLIDE_VERSION

And then continue deployment with gdeploy tool.