No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Untitled.txt

I'm not totally sure, but that bucketname doens't look correct, the `bucket` parameter should be your bucket name

it can, but you've stringified it, rather than referencing the output directly

try this
```bucket: arn:aws:s3:::arn-code,```

I just realized that it says access point arn.

are you creating the bucket with pulumi too, or referencing an existing bucket?

What i'm trying to do is create the bucket in a different pulumi plan so that I can have one that generates globally accessible resources and another that shares some of those resources. Is that possible?

I tried using getBucket, but that doesn't accept an arn.

if I use Bucket constructor with arn option will that reference the existing bucket?

yeah try that, to answer your other question, you can reference the bucket from another pulumi project using a stack reference: <https://www.pulumi.com/docs/intro/concepts/organizing-stacks-projects/#inter-stack-dependencies>

so I have to export the bucket then in the one project then reference it in the other?

Yes. Be aware that (afaik) StackReferences don't work with some backends. They might work only with the default (Pulumi) backend?

Looks like I still get the same issue using the referenced object from the other stack.

Untitled

This seems to produce the right bucket name on the first line, but fails with the same message afterwards.

<@U012UJTT55M> stack references work with all backends, there are issues reference stacks if you have different state buckets between projects but there's no reason you can't use stack references for other backends

Ah. We store all our state in different paths in the same S3 bucket and haven't been able to get them to work...

the different paths is the problem I think