Please enable JavaScript.
Coggle requires JavaScript to display documents.
AWS Route 53 and CloudFront download download (CloudFront download…
AWS Route 53 and CloudFront 
CloudFront
If your cache expiration times are too short, you may have request from the edge location to the origin occurring when they are not required. If you increase the cache expiration date, you should experience less hits to the origin.
-
If the cache expiration time is not set (or set to zero), then CF will not cache objects at the edge location. This will prompt the behavior where the edge location will have to request the same object from the origin for reach request.
Once an object is cached at an edge location, all other requests for that object will be handled by the edge location, not your application. This can significantly reduce the amount of times your resources are hit.
A CloudFront origin is the source of the object, and an edge location is where the object is cached.
-
-
CDN of AWS : Content Delivery Network - Large distribution of caching servers. Routes viewers to the best location. Caches appropriate content at the edge. Accelerates dynamic content. Provides scalability and performance of applications.
-
-
-
Components
Origins
Access restriction via OAI, signed URL, or Origin Custom Header
-
-
-
-
-
-
Distributions
-
-
-
Contain specific configurations and tags (i.e. origins, behaviors, error pages, restrictions)
Restrictions, error pages, tags
-
-
-
Route 53
An alias record set contains a point to an AWS-specific resource and is used to direct traffic to ELBs, CF distributions, and S3 buckets.
An alias record set contains a point to an AWS-specific resource and is used to direct traffic to ELBs, CF distributions, and S3 buckets.
You will need to configure the record set as a type "A" alias. An alias allows you to point the domain to an AWS-specific endpoint, such as an ELB, Cloudfront distribution, or S3 bucket (as opposed to just an IPv4 IP address).
To use an S3 bucket for Route 53 DNS failover, the bucket name must match the domain name.
-
The opposite is true: A public hosted zone should be used for routing Internet traffic for a domain, and a private hosted zone should be used for routing traffic within a VPC.