Marg Amazon CloudFront

it's AWS so it can't be too bad. Also it can be easily automated with cloudformation or Terraform.

Domain name stuff. We were trying to replace what we did in CustomDomainName api gateway and it wasn't easy to do in Cloud Front.

don't do it.

API gateway could not restrict tls 1.2 so we had to use cloudfront.

....................................................

I've tried to setup a simple s3 hosted webside with some additional lambdas and I got to the point that I needed to configure https for the domain name. Cloud front was involved there. There an issue somewhere and I don't even know how to debug it. I mean : I've tried to use it for a simple thing and ive ended up reading a ton of documents and still don't understand what went wrong... Didn't make this https still because of it...no time left on this task for now...

None or minus 1$/month

Cloud Front provides really good performance compared to other platforms out there. it does come with a cost due.

If you use other services of Amazon Web Services then this is a no brainer.

The API is documented very bad but it works and it's flexible.

The main advantage is the pricing, there is not competition right now that makes it as affordable as Amazon's Cloud Front.

The only Good part of This is the API, they have it well wrapped in more the a few SDK's making the technical work with Cloud Front not so bad, assuming you are a programmer.

Using this product is complicated like hell! you really need to know what you are doing or have a lot of patience. the documentation is endless and not clear at all.

Also, Amazon is a company with a lot of resources, hire a UX person already!

You will probably use this because you were forced to. try and look at other options first.

Try to look external tools that wrap around the API and make the use of this product a little bit less horrible.

I use Cloud Front for a few small business websites.

I don't want to use it, but i have to because I need SSL for those websites and they are statically hosted on S3.

Sometimes it seems easier to just start a simple instance and setup static file hosting using nginx on it then setting up Cloud Front.

I like that it's already integrated with other AWS services easily, but that's about it. It also seems very highly customizable.

It's really hard to use. Seriously. You really need to know what you're doing. I supposed you could always improve UI/UX, but I think that’s already pretty decent. I’m sure it could probably run faster too, but that’s still not that bad either. Amazon also keeps updating/changing their user interface, so we're having to re-learn how to set things up again periodically. Despite the redesigns, our CloudFront distributions continue to crash on us frequently and create problems when configured with DNS.

If you really really really know what you're doing, then this could be a viable option, but if you want to sleep well at night and not have to really think hard about setting up CDN and DNS then you might want to go with another provider until Amazon gets their stuff together here.

We tried using CloudFront but because it kept crashing, we ended up not using it heavily.

The size of the storage of the pops in India are good

Latency in India in the tier 2 and beyond is not too great

Content delivery for media