#operations #integrations #storage
Overview
By default, contentbird stores images and files in its own asset management system via a CDN. Alternatively, you can connect your own Amazon S3 bucket and use it as external storage.
Requirements
To set up the integration, you need:
access to an S3 bucket
valid credentials (Access Key & Secret Key)
permissions for uploading and accessing files
Setup in contentbird
📍 Project Settings → Digital Asset Management
Here, you can configure and connect your S3 bucket.
Required information
To establish the connection, enter the following details:
Access Key
Secret Key
Bucket Name
Region (e.g., eu-central-1)
👉 You can find these details in your AWS account.
How it works
After successful integration:
media files are stored directly in your S3 bucket
contentbird accesses these assets from your bucket
your external storage replaces the internal CDN for assets
Benefits of S3 integration
use of existing cloud infrastructure
scalable storage capacity
centralized asset management
greater control over data and hosting
Best practices
grant only the necessary permissions (security first)
use a clear bucket structure for better organization
regularly review access and permissions
test the setup with a sample upload
Conclusion
Integrating an AWS S3 bucket allows you to extend your asset management flexibly and align it with your existing cloud infrastructure.
This is especially beneficial for larger teams or companies with specific hosting requirements.