This message was deleted.

For most resources, you can specify a

name

argument to override the default auto-naming. For buckets, it's (unfortunately) inconsistent, but you can accomplish this by specifying a

bucket

argument. So, for example:

let buck = new aws.s3.Bucket("foo", {
    bucket: "foo-exactly",
    // other args, as usual...
});

The resulting name will be

foo-exactly

. The auto-naming is to ensure it's easier to stand up multiple stacks side-by-side without any naming conflicts, but completely understood that sometimes you need the exact name.

thanks Joe btw we should catch up soon. Today went well with my boss

Excellent to hear! Would love to. I'll shoot you a mail.

yes please do. We have next steps.