Not able to configure a working cname for Amazon S3

[SMLMATS]

I try to configure my cname for amazon s3 and it's not working

I used this
servea.imgmax.net. CNAME s3.amazonaws.com
servea.imgmax.net. CNAME servea.s3.amazonaws.com

 

[Rodolfo]

I'm sorry to hear about that you are experiencing issues creating a CNAME record. You should read these:

• http://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingCustomURLs
  
• https://havecamerawilltravel.com/photographer/how-set-cname-for-amazon-bucket
  
• http://stackoverflow.com/questions/...-cname-for-an-s3-bucket-using-amazon-route-53
  
• https://carltonbale.com/how-to-alias-a-domain-name-or-sub-domain-to-amazon-s3/

Please note that CNAMEs are settings that you configure for your domain (DNS stuff), it has nothing to do with the script itself or even your server settings.

 

[SMLMATS]

Thanks Rodolfo, fast support loving this.
I followed this http://stackoverflow.com/questions/...-cname-for-an-s3-bucket-using-amazon-route-53
willglynn explains it very well
the second link I tried but wasn't much clear
https://havecamerawilltravel.com/photographer/how-set-cname-for-amazon-bucket

 

[Rodolfo]

Basically a CNAME is a named alias, for example:



That maps translate.chevereto.com to that onesky subdomain. CNAMEs are just any other DNS setting so it needs time to propagate. My recommendation is that you should use CloudFlare for DNS settings, is fast, easy and free. I have CloudFlare on Chevereto.com just for the easiness and fast propagation of the DNS settings, I'm not using their cache or CDN at all.

 

[SirMoo]

You may be linking your bucket a bit wrong. It's highly misleading.

For instance... my bucket looks like this. amz.site.tld.s3-us-west-2.amazonaws.com

My cname looks like amz.site.tld

The bucket name needs to be the full domain of the cname, not just the cname part.

This means you need to name your amazon bucket servea.imgmax.net