Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StackSetsResource: TemplateURL to another account and ergion #168

Closed
ihr opened this issue Mar 14, 2019 · 1 comment
Closed

StackSetsResource: TemplateURL to another account and ergion #168

ihr opened this issue Mar 14, 2019 · 1 comment
Labels

Comments

@ihr
Copy link

ihr commented Mar 14, 2019

Hi,

StackSetsResource template is really great and helps a lot, so thank you for creating it.

I would like to report a problem that I am having. I have an account "A" in a region - eu-central-1, which holds a template that is to be referenced by the StackSet Custom Resource (i.e. via the Lambda) in account 'B' in region us-west-1. I am getting this error:

Failed to update resource. Unexpected error: An error occurred (ValidationError) when calling the UpdateStackSet operation: Must reference a valid S3 object to which you have access. (See CloudWatch Log Stream:

the TemplateURL is pointing to: https://s3.eu-central-1.amazonaws.com/<bucket>/tempate.yaml

I have customised the Custom Resource Lambda to use TemplateBody and I use:

  TemplateBody:
    Fn::Transform:
      Name: AWS::Include
      Parameters:
        Location: !Sub 's3://${ArtifactBucket}/https-certificate.yaml'

and this works. However, there are some limitations due to using AWS::Include, such as one cannot use Ref in the Outputs section and also the size of the template

@mleziva mleziva added the bug label Oct 6, 2023
@ericzbeard
Copy link
Contributor

Cleaning up stale issues in preparation for refreshing this repository. Please re-open if this still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants