Thanks Dirk.. That sounds good.

Thanks for that reply Dirk.

I think what you are referring to is quite applicable when the CDN is setup via using a S3 bucket. I followed the following guide to setup my CloudFront CDN:

https://www.doitwithwp.com/set-up-w3-total-cache-with-amazon-cloudfront-cdn

Here are the 2 problems that I'm facing currently:

1. The images appear at multiple CDN locations - http://cdn5.sarkarilife.com/wp-content/uploads/2015/01/bank-awareness-gk-ibps-bank-exams.jpg as well as http://cdn1.sarkarilife.com/wp-content/uploads/2015/01/bank-awareness-gk-ibps-bank-exams.jpg .

2. The same image is not available at the original location - http://sarkarilife.com/wp-content/uploads/2015/01/bank-awareness-gk-ibps-bank-exams.jpg

Looking forward to your response.

I just setup Cloudfront CDN through W3 Total Cache. Everything looks good but there is one problem that I have encountered:

After activating the CDN none of the images are available at the older image URLs and they are throwing a 404 error.

Let me give you an example for this:

1. Before I setup the CDN, let's say an image was available at http://example.com/wp-content/uploads/2015/03/leap-of-faith.jpg

2. After I setup the CDN, the image is available at http://cdn.example.com/wp-content/uploads/2015/03/leap-of-faith.jpg and the good part is the URLs in the blog posts where this image was attached is updated to reflect the above mentioned URL. But the problem is that when visit the older URL of the image (which is what Google has crawled earlier, I get a 404 error).

Can you help me how to avoid this problem?

Ravi C