
A private storage object that opens for you is not automatically readable by Cloudinary. Importing from a private bucket requires the provider's documented authorization and read access, with additional encryption permissions where applicable. Do not make an entire client-photo bucket public merely to repair an import.
Key Takeaways
- Your signed-in browser and the media provider are different readers.
- Bucket allowlisting and object-read permission are separate checks.
- Encrypted objects can require access to the actual encryption key.
Identify the source reader
Cloudinary's upload-source documentation describes importing from private Amazon S3, Google Cloud Storage and Azure storage. Each route has its own setup, including a documented allowlist marker and provider read access.
For S3 objects encrypted with AWS KMS, the same page says Cloudinary also needs permission to use the relevant KMS key. A bucket policy alone may therefore be insufficient.
This procedure concerns an authorized private-storage integration. It does not turn a browser preview address into a remotely available source.
Give the storage owner a narrow diagnostic record
- Record the correct product environment, source bucket and intended object privately.
- Confirm that the object exists and is the approved source.
- Identify the documented storage URL form for that provider.
- Have the storage administrator verify the required allowlist marker for that Cloudinary environment.
- Verify provider read access for the intended storage location.
- For encrypted S3 objects, compare the object's actual KMS key with the granted key policy.
- Import a non-sensitive sample and inspect the resulting asset.
Use the current official setup instructions for the exact provider. Do not copy a policy intended for backup storage, which has a different purpose, into an ingestion workflow without review.
A hypothetical encrypted portrait archive
An imagined studio imports approved portraits from an encrypted S3 archive. The operator can open a source through their own account, but the import fails after the bucket policy was configured.
The proposed investigation checks the object's encryption-key identity. If it uses a different key from the one authorized for the service, that is a concrete remaining dependency. Recompressing the JPEG cannot repair that authorization mismatch.
This is a planning example, not a claim that the cause of any real account failure has been established.
Verify the imported copy and its scope
After an authorized sample succeeds, inspect subject identity, dimensions and the returned asset identifier. Confirm the selected delivery type before exposing a rendition. Successful private ingestion does not by itself make the destination asset private.
The temporary image-link guide addresses public crawler delivery, while the browser object-URL guide addresses local preview references. Neither replaces private storage's provider authorization.
Accept when the intended service can import the approved object through the documented private route and the destination has the intended access policy. Keep credentials, signed source addresses and unrelated client objects out of public troubleshooting evidence.
Related tasks
- Why Does a blob: Image Link Open for Me but Not for My Client?
- Can I Use a Temporary AI Download Link as My Product Feed Image URL?
- How Do I Check a Photo for Location Metadata Before Sharing It?
Sources and scope
- Cloudinary: Customizing uploads: Backend SDK image resource default, browser auto resource detection, audio as video, input-source requirements, private-storage allowlisting/read/KMS permissions, Python stream filename requirement, public-ID naming/overwrite, and environment-dependent metadata retention.
Documentation-based editorial synthesis with AI-assisted research and drafting. Scenarios, ledgers and acceptance checks are hypothetical or proposed. No hands-on test, account change, measured demand, AI-citation rate, benchmark or client acceptance is claimed. Availability and plan limits remain within each cited source's scope.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.