What actually lands in the bucket
Amazon S3 is the AWS object storage service: files live in buckets tied to a region and are accessed through an API. In Endora Commerce, S3 is one of three storage backends for the assets library, next to Google Cloud Storage and local disk. Exactly one is active at a time, and the platform starts on local disk by default.
The library holds images, video, PDFs and other documents, which are then used in several places:
- product image galleries and category main images,
- product attachments, such as technical data sheets or declarations,
- files for downloadable virtual products,
- images and documents embedded in CMS pages.
Other modules use the same store. Product feed files, for example for Google Merchant Center, are written to the bucket as private objects, under their own prefix and outside the assets library, and are served to the outside world by the platform itself, not by an S3 address.
Public and private: what it means in S3
Visibility is set per asset, not once for the whole bucket.
- A public asset has a stable address. By default it is the bucket address in its region; once you provide your own domain or a CDN address, links are built on that instead.
- A private asset has no stable address. On every read the admin panel or the storefront receives a fresh signed address (a presigned URL, V4-signed by the AWS SDK), valid for 300 seconds by default. The lifetime is a setting.
For a B2B buyer this means a document link copied from the browser and forwarded stops working after a few minutes. Two things follow from how S3 itself works: a signed address works for anyone who holds it until it expires, and with long-lived IAM user keys its lifetime cannot exceed 7 days.
What to prepare on the AWS side
- A bucket in the region of your choice. For companies in Poland and the EU this will usually be a European region.
- An IAM user with an access key, restricted to that one bucket. The platform uploads, reads and deletes objects, changes their ACLs and checks that the bucket is reachable, so the policy should cover
s3:PutObject,s3:GetObject,s3:DeleteObject,s3:PutObjectAclands3:ListBucket. - A decision about ACLs. Asset visibility is translated into an object ACL (
public-readorprivate), while new buckets have ACLs disabled by default (the “Bucket owner enforced” setting) and Block Public Access turned on. In that configuration S3 rejects an object write that carries any ACL other than bucket owner full control. If public files are to be served straight from the bucket, you need to deliberately enable ACLs and allow public ACLs. The AWS documentation covers the details: Object Ownership.
Settings in the admin panel
Configuration lives in Settings, in the Storage group.
| Setting | What it is for |
|---|---|
assets.s3.bucket, assets.s3.region | Bucket name and region, both required |
assets.s3.access_key_id, assets.s3.secret_access_key | The IAM user’s key |
assets.s3.prefix | Optional key prefix, useful when the bucket is shared with another system |
assets.s3.public_base_url | Optional CDN or custom domain address for public files |
assets.s3.endpoint | Optional endpoint of an S3-compatible service, such as MinIO |
After saving you can call the connection test (POST /api/v1/admin/assets/storage/self-check), which checks whether the bucket is reachable with the credentials provided.
Two things worth knowing before go-live:
- Access to Settings should be limited to trusted people, and the IAM key should have no permissions beyond this bucket.
- Switching the backend does not move files. Each asset remembers where it was stored and is read from there, so after moving from local disk to S3 the old files stay on disk and new ones go to the bucket. Both backends have to remain available.
Deleting files
A deleted asset disappears from listings but can be restored for 30 days by default. Only then does a background process remove the object from the bucket, and if S3 refuses, for example after the key has been revoked, it retries. A file used by a product, a category or a CMS page cannot be deleted until it is detached.
When to pick S3, and when something else
- S3: when your infrastructure already runs on AWS, the application runs as more than one instance, or files should have copies and versioning independent of the application server.
- Google Cloud Storage: when the rest of the environment is on Google Cloud. The visibility model and the settings follow the same pattern.
- Local disk: for development and simple single-server deployments, provided the volume holding the files is backed up together with the database.
The other infrastructure and business integrations are collected on the integrations page.