Switching over to managed cache/origin policies, general advice

[rromanchuk]

I'm trying to diff whats currently in the cloudformation template using the legacy DefaultCacheBehavior and was looking for guidance on if there is an existing policy that work well with this deployment.

I'm currently testing Managed-CORS-CustomOrigin and Managed-CachingOptimized, just looking for a second pair of eyes to check if i'm missing anything obvious.

I deployed on a staging environment and there is a distinct increase in cache hits on deployment date, still need to verify i didn't break something else though.

Reference:
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-managed-origin-request-policies.html
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-managed-cache-policies.html

[beomseoklee]

@rromanchuk Thanks for your opinion.

We haven' considered to use the managed cache policy and origin request policy, but we will investigate this one. If no managed policy fits into our case, we might think to create a custom policy. Since we are using the legacy cache setting, it could be valuable to use new settings instead of the legacy cache settings.

[G-Lenz]

We've added a CloudFront cache policy and a CloudFront origin request policy in v5.2.0.