For SST/Cloudformation best practices, is it bad to build multiple stacks that depend upon each other? eg. The ARN of an S3 bucket is export into our Lambdas, and now we cannot make modifications to the S3 bucket

Hey @Drew, if you export the Bucket ARN and imports it into the Lambda, you won’t be able to remove the Bucket directly, you’d have to break the dependency first. But you can make changes to it, ie. updating permission, life cycle policy, setup static site, etc.

Yep, I think that’s exactly it

Yeah, you can add this to the Bucket’s stack:

this.exportValue(bucket.bucketArn)

Is there a better way? Should we avoid referencing resources in other stacks?

Usually the bucket’s ARN is exported automatically behind the scene when you reference it in another stack.

🤔 I’ll try

And if you remove all the references to it, the export is also removed.

Ya, it should automatically be exported.

Because CFN will deploy the stack with the bucket first, and tries to remove the export. But the export is still in use, b/c other stacks are still referencing it (u haven’t deployed the other stacks yet).

Yes! That!

So by adding

this.exportValue(bucket.bucketArn)

you are telling CDK to always export the ARN, even no one is referencing it.

Starting from the downstream…… Oh, just use exportValue() ✅

1. add

this.exportValue(bucket.bucketArn)

and remove all references to the ARN 2. deploy 3. rename s3 bucket, add the references back 4. deploy

Beauty! Frank you’re my hero! I’ve got a plan

lol nah we need to document this better

ha, you say that all the time too