Create Bucket
Creates a new S3 bucket in the specified AWS region or S3-compatible storage service.
Common Properties
- Name - The custom name of the node.
- Color - The custom color of the node.
- Delay Before (sec) - Waits in seconds before executing the node.
- Delay After (sec) - Waits in seconds after executing node.
- Continue On Error - Automation will continue regardless of any error. The default value is false.
If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.
Inputs
- Client Id - The client connection ID from the Connect node. Optional if using credentials directly.
- Bucket Name - The name for the new bucket. Must be globally unique across all AWS S3 buckets and follow S3 naming rules.
Options
- Region - (Optional) The AWS region where the bucket will be created (e.g.,
us-east-1,eu-west-1,ap-southeast-1). If not specified, the bucket will be created in the default region. - End Point - S3 endpoint URL. Required only if using credentials directly instead of Client ID.
- Access Key Id - AWS Access Key ID credential. Optional - use this instead of Client ID for direct authentication.
- Secret Key Access - AWS Secret Access Key credential. Optional - use this instead of Client ID for direct authentication.
How It Works
The Create Bucket node creates a new S3 bucket with the specified name and region. When executed, the node:
- Retrieves the S3 client using either the Client ID or creates a new client from credentials
- Validates that the bucket name is provided and not empty
- Retrieves the optional region parameter
- Sends a request to S3 to create the bucket with the specified options
- Completes successfully once the bucket is created
Requirements
- Either a valid Client ID from a Connect node, or Access Key ID and Secret Access Key credentials
- A unique bucket name that follows S3 naming conventions
- Appropriate S3 permissions to create buckets (s3:CreateBucket)
Bucket Naming Rules
S3 bucket names must follow these rules:
- Must be between 3 and 63 characters long
- Can contain only lowercase letters, numbers, hyphens (-), and periods (.)
- Must begin and end with a letter or number
- Must not be formatted as an IP address (e.g., 192.168.5.4)
- Must be globally unique across all AWS accounts
- Cannot contain uppercase letters or underscores
- Cannot have consecutive periods or hyphens next to periods
Error Handling
The node will return specific errors in the following cases:
- Empty or invalid bucket name
- Bucket name already exists (globally across all AWS accounts)
- Invalid Client ID or credentials
- Insufficient permissions to create buckets
- Invalid region specified
- Network or connection errors
Usage Notes
- Bucket names must be globally unique across all AWS S3 accounts
- Once created, a bucket name cannot be changed
- Newly created buckets are private by default
- Region selection affects latency and compliance requirements
- Some regions may require additional setup or account verification
- Bucket creation is eventually consistent - it may take a moment before the bucket appears in all regions
- Creating too many buckets in rapid succession may be rate limited
Best Practices
- Use descriptive, meaningful bucket names that indicate purpose
- Include environment identifiers in bucket names (e.g.,
myapp-production-data,myapp-dev-uploads) - Choose a region close to your users for better performance
- Consider data residency and compliance requirements when selecting a region
- Use lowercase letters and hyphens for consistency
- Avoid creating excessive numbers of buckets (S3 has a default limit of 100 buckets per account)
- Document your bucket naming convention for team consistency
Example
To create a bucket for storing application logs in the US East region:
Inputs:
- Client Id: (from Connect node)
- Bucket Name:
my-company-app-logs-2024
Options:
- Region:
us-east-1
Result:
The bucket my-company-app-logs-2024 will be created in the us-east-1 region and will be immediately available for file uploads.
Direct Credentials Example
You can also create a bucket without using the Connect node by providing credentials directly:
Inputs:
- Bucket Name:
my-app-data-bucket
Options:
- Region:
eu-west-1 - End Point:
s3.eu-west-1.amazonaws.com - Access Key Id: (your AWS Access Key ID credential)
- Secret Key Access: (your AWS Secret Access Key credential)
This approach is useful for one-off operations or when you need different credentials for different buckets.
Regional Endpoints
For better performance, use regional endpoints:
- US East (N. Virginia):
us-east-1 - US West (Oregon):
us-west-2 - Europe (Ireland):
eu-west-1 - Europe (Frankfurt):
eu-central-1 - Asia Pacific (Singapore):
ap-southeast-1 - Asia Pacific (Tokyo):
ap-northeast-1 - Asia Pacific (Sydney):
ap-southeast-2
See the AWS Regions documentation for a complete list of regions.