(aws-cloudfront): EdgeFunction us-east-1 helper stack created in different account #12789
Assignees
Labels
@aws-cdk/aws-cloudfront
Related to Amazon CloudFront
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
in-progress
This issue is being actively worked on.
p1
Comments
danilobuerger
added
bug
github-actions
bot
added
the
@aws-cdk/aws-cloudfront
njlynch
added a commit
that referenced
this issue
Feb 15, 2021
…count The us-east-1 stack for EdgeFunction was defaulting to the default deploy account. This means that using one account to deploy, and another for the stack which contains the EdgeFunction, the support stack in us-east-1 will be deployed into the deploy account, rather than stack account. This fix has the us-east-1 stack inherit the account from the parent stack. fixes #12789
njlynch
added
effort/small
mergify bot
pushed a commit
that referenced
this issue
Feb 15, 2021
…count (#13055) The us-east-1 stack for EdgeFunction was defaulting to the default deploy account. This means that using one account to deploy, and another for the stack which contains the EdgeFunction, the support stack in us-east-1 will be deployed into the deploy account, rather than stack account. This fix has the us-east-1 stack inherit the account from the parent stack. fixes #12789 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
NovakGu
pushed a commit
to NovakGu/aws-cdk
that referenced
this issue
Feb 18, 2021
…count (aws#13055) The us-east-1 stack for EdgeFunction was defaulting to the default deploy account. This means that using one account to deploy, and another for the stack which contains the EdgeFunction, the support stack in us-east-1 will be deployed into the deploy account, rather than stack account. This fix has the us-east-1 stack inherit the account from the parent stack. fixes aws#12789 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using a EdgeFunction inside a environment stack the us-east-1 helper stack is created in a different account (the one with the aws credentials)
Reproduction Steps
Use demo from https://docs.aws.amazon.com/cdk/api/latest/docs/aws-cloudfront-readme.html#lambdaedge
Created it inside environment stack (with account "A") and deploy with aws credentials of account "B".
What did you expect to happen?
us-east-1 helper stack should be deployed to account "A"
What actually happened?
us-east-1 helper stack is deployed to account "B"
Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: