skip to Main Content

I have git sync in cloudfomation to trigger my nested stack, that triggers other cloudformation templates.

But the templates URLs are for s3.

Is there not a convenient way to have built nested stacks from github alone without any cp templates to bucket or other weird work arounds?

edit: What is the purpose of git sync, when you have to copy templates to s3 anyway, when using nested stacks?

2

Answers


  1. AWS does not natively support deploying Cloudformation stacks from Github as the templateUrl must be an S3 bucket [1]. While they could create this extension, S3 is their technology and they would prefer to have all Cloudformation code contained within their ecosystem.

    The purpose of git sync is to keep your local workspace in sync with the remote git repository. It is not related to AWS.

    [1]
    https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudformation-stack.html#cfn-cloudformation-stack-templateurl

    Login or Signup to reply.
  2. Git sync in Cloudformation automates updates for the main stack but nested stack templates still need to be stored in S3 as github URLs aren’t supported directly. To streamline this try using a CI/CD pipeline eg. AWS CodePipeline or github actions to automatically upload templates from github to S3 to ensure CloudFormation can access them without manual uploads.

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search