You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a list of buckets accordingly to this scheme <BUCKET_PREFIX>-<REGION> outside the scope of my CDK app, each with these bucket-permissions:
if deploying to one single region yes you would have just one bucket. but you still need to name the bucket with the {prefix}-{region} naming convention and for consistency it is still a list. the reason it was done this way is due to how the resulting cloudformation template can be parameterized. for stacksets, we get one template that is used across all accounts/regions the stackset is deployed to so this limits flexibility. we can have a hardcoded prefix that is shared across all asset buckets then use cfn pseudo parameters to make it region specific and allow different buckets for different regions as required by the lambda service.
this is a big difference compared to how single stacks are deployed with cdk deploy since the bucket name for each region would be hardcoded and each region would get its own cfn template.
for your error, i would recommend looking at cloudtrail in the account throwing the error.
I would like to leverage
cdk-stacksets
in order to deploy multiregional and into multiple accounts including File Assets.Environment:
I have created a list of buckets accordingly to this scheme
<BUCKET_PREFIX>-<REGION>
outside the scope of my CDK app, each with these bucket-permissions:Then I imported the bucket, assigned the
assetBucket
andassetBucketPrefix
in order to create the stack:This is my SteckSetTemplate:
When I run
deploy
I get the error message:Accordingly to #428 permissions for the AwsApiCall are not being created, however he fixed it, without mentioning the fix.
assetBuckets
-array, if so why is it an array?assetBuckets
be an array of every regional asset bucket, then whats the point ofassetBucketPrefix
?Please clarify.
The text was updated successfully, but these errors were encountered: