Spaces CDN read VS write files and Django settings?

Hi there,

When integrating Django with DigitalOcean Spaces using the CDN, the AWS_S3_CUSTOM_DOMAIN typically refers to the CDN endpoint of the Space for reading (i.e., serving static/media files). The purpose of using the CDN endpoint is to distribute the content globally to reduce latency for users fetching those assets.

For writing (i.e., uploading files to the Space), Django will use a different endpoint which will be the DigitalOcean Space’s endpoint (not the CDN endpoint). This distinction is managed internally by the libraries you use (like django-storages with the S3 backend).

To clarify:

1. Reading Files (Serving): Your Django app will serve static and media files using the CDN endpoint (e.g., your-space-name.nyc3.cdn.digitaloceanspaces.com). This is where AWS_S3_CUSTOM_DOMAIN comes into play when you want to serve these assets using the CDN.

2. Writing Files (Uploading): When your Django app needs to upload a file to the Space, it will use the endpoint associated with your Space directly (e.g., nyc3.digitaloceanspaces.com). This is typically managed through the AWS_STORAGE_BUCKET_NAME and AWS_S3_REGION_NAME settings in conjunction with the library.

To answer your concern directly: No, you don’t need to configure separate read and write URLs in your Django settings when using the typical django-storages setup for DigitalOcean Spaces. The AWS_S3_CUSTOM_DOMAIN is primarily for reading (serving) files through the CDN, while writing (uploading) is managed internally by the library.

Best,

Bobby