Try our conversational search powered by Generative AI!

Using CDN and still serving Friendly Names for Images


We are hosting our website in AWS. We are also trying to use AWS Cloudfront as our CDN.

We have run into an issue with naming our images in a friendly manner and I was wondering how others have solved this problem.

We are using AWS blob provider from EPiServer. When new content is being authored the images are automatically stored in  AWS S3 buicket.

When EPiServer uploads images to S3 bucket it uses long generic names.


AWS Cloud front recommends serving images directly out of S3 bucket and serving dynamic pages from AWS EC2 instances.

We use the URL rewriting sample code from github and were able to update the image URL's so CDN URL was inserted into it.

Images are automaticaly cached. This is working well but the URL for the image is not SEO friendly. It looks like this:

We want to use friendly names for our images. The only way we can get CDN to work is if We place our entire website behind CloudFront CDN. We stopped doing URL rewiting. Now images are cached and we also get friendly URL's. Only thing we don't like about this approach is that now we are serving images out of our Web Server. This is putting unnecessary load on the web server. Ideally we want to serve images out of AWS S3 bucket.

Is there another way to meet our needs? Have you been able to serve images directly from Azure or AWS blob storage and still use friendly names.

Thanks for any suggestions you have for us.

Dec 15, 2015 21:35

As you write you would need something between the storage and the CDN to get friendly names.

I think the easiest way to route files through CDN with friendly names is to have a CDN-solution that can do origin-pull and install in your site.

Dec 16, 2015 8:32
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.