AWS S3: How to Create Multiple Buckets Efficiently

Select Language:

Creating multiple Amazon S3 buckets within a single CDK stack can sometimes lead to errors, especially if the bucket names are not unique or already exist elsewhere. The error message you’re seeing typically means that some of the bucket names you’ve chosen are already taken or are conflicting with existing buckets, as S3 bucket names need to be unique across all AWS accounts.

To fix this, you have a couple of options. The simplest way is to allow the CDK to automatically generate unique bucket names for you. This ensures each bucket has a globally unique name without manual effort. However, if you need to keep specific names for your buckets, you will need to verify those names are not already in use and make sure they’re truly unique.

Here’s an example of how to create multiple S3 buckets in a single CDK stack while keeping their specific names:

typescript
import as cdk from ‘aws-cdk-lib’;
import as s3 from ‘aws-cdk-lib/aws-s3’;
import { Construct } from ‘constructs’;

export class MyS3Stack extends cdk.Stack {
constructor(scope: Construct, id: string, props?: cdk.StackProps) {
super(scope, id, props);

// Create each bucket with a specific name
const backendAppBucket = new s3.Bucket(this, 'BackendAppBucket', {
  bucketName: 'backend-app',
  removalPolicy: cdk.RemovalPolicy.DESTROY, // this allows deletion when stack is deleted
});

const backendQueueBucket = new s3.Bucket(this, 'BackendQueueBucket', {
  bucketName: 'backend-queue',
  removalPolicy: cdk.RemovalPolicy.DESTROY,
});

const backendCostBucket = new s3.Bucket(this, 'BackendCostBucket', {
  bucketName: 'backend-cost',
  removalPolicy: cdk.RemovalPolicy.DESTROY,
});

const backendDataBucket = new s3.Bucket(this, 'BackendDataBucket', {
  bucketName: 'backend-data',
  removalPolicy: cdk.RemovalPolicy.DESTROY,
});

// Output the bucket names for reference
new cdk.CfnOutput(this, 'BackendAppBucketName', {
  value: backendAppBucket.bucketName,
  description: 'Backend App Bucket Name',
});
new cdk.CfnOutput(this, 'BackendQueueBucketName', {
  value: backendQueueBucket.bucketName,
  description: 'Backend Queue Bucket Name',
});
new cdk.CfnOutput(this, 'BackendCostBucketName', {
  value: backendCostBucket.bucketName,
  description: 'Backend Cost Bucket Name',
});
new cdk.CfnOutput(this, 'BackendDataBucketName', {
  value: backendDataBucket.bucketName,
  description: 'Backend Data Bucket Name',
});

}
}

Keep in mind, if you want to keep the same specific bucket names, you need to make sure those names don’t already exist—either in your account or globally. If a bucket with the same name exists, your deployment will fail.

If you’re repeatedly deploying and need the buckets to be destroyed when deleted, setting removalPolicy: cdk.RemovalPolicy.DESTROY helps. But for production environments, consider more persistent policies.

Before deploying, double-check that none of these bucket names are already in use. You can do this via the AWS console or CLI. If a name conflict occurs, you’ll need to change the name or delete the existing bucket before redeploying.

With this approach, you should be able to create all your buckets in one stack while keeping your desired names intact.