Uploadcare allows you to upload files directly to your AWS S3 storage.
Adaptive bitrate streaming is not supported for files uploaded directly to AWS S3 buckets.
You may want to choose this option when you:
You need an Amazon Web Services account with creating a new or selecting an existing bucket in S3 bucket management.
Note: AWS S3 storage is available on the Enterprise plan. Contact our sales.
Enter your AWS S3 console and configure your S3 bucket:
johnsbucket1.<bucket> with the name of your AWS S3 bucket):
Connect the S3 bucket to Uploadсare in the following ways:
To connect your own AWS S3 bucket to the new Uploadcare project:
Uploadcare will run tests to ensure it can connect and upload the files to the bucket.
Add the S3 bucket to an existing project without uploaded files:
Note: Uploadcare only handles files uploaded through our service. We recommend starting with an empty bucket.
When uploading bigger files, we’re using multipart uploading and upload file chunks to S3 directly. If you’re using CSP, add the appropriate CSP to your webpage(s):
You can change addressing style for your S3 bucket via Support.
When you delete a file via Uploadcare, the file disappears from the Dashboard and is marked as removed. You can delete a file in the Dashboard or via the REST API Delete file method.
The file metadata may still be accessible via the API until the final cleanup process runs.
The object stored in your AWS S3 bucket is permanently deleted 90 days after the file is marked as removed.
Unstored files are automatically marked as removed 1 day after upload and disappear from the Dashboard and API responses at that time. They then follow the same deletion lifecycle.
Uploadcare deletes only objects created through Uploadcare. Objects stored in the bucket by other systems are not affected. We recommend using the connected bucket exclusively for Uploadcare-managed files.