• Resolved scoyodesign

    (@scoyodesign)


    Does this plugin use CloudFront as a simple URL redirect or does it actually cache objects at an edge location? I ask because when I upload an image with a Minimum, Maximum, and Default TTL of 60 seconds the image is immediately available. It usually takes time for the object to be cached and available, in this case, it should take about 60 seconds due to the TTL settings.

    When I access my CloudWatch dashboard I don’t see the requests, or bytes uploaded/downloaded from the CloudFront distribution I set up with this plugin. I want to be certain these objects are being cached at an edge location and not rendered from my server.

    Could you please clarify for me?

    Thanks

    • This topic was modified 5 years, 4 months ago by scoyodesign.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author luckychingi

    (@luckychingi)

    hello @scoyodesign

    The AWS CDN plugin caches objects on edge locations, you can see the details in cache statistics and popular objects

    The plugin will check if the object exists in Cloudfront cache, if not, it will show object from source (the website) and cache it. If found in cache, the object will be fetched from Cloudfront.

    If the cache has expired, it will show the object from source and re-fetch it.

    Please refer to this article to test cloudfront

    Are you using 60 seconds TTL to test cloudfront? You can check x-cache headers on Google chrome developer console too.
    https://i.stack.imgur.com/1dolH.png

    Thread Starter scoyodesign

    (@scoyodesign)

    Thank you for your fast reply!

    Awesome, I just wanted to be certain since I’ve never used this plugin before. Thanks for the documentation. Yes, I’m using 60 second TTL just for testing purposes.

    Plugin Author luckychingi

    (@luckychingi)

    You are welcome @scoyodesign

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Caching and Storage’ is closed to new replies.