---
title: "Discussion on \"CloudFront Overview and CloudFront with S3: A Detailed Guide\" | Hashnode"
description: "Discussion on \"CloudFront Overview and CloudFront with S3: A Detailed Guide\". 📢 Day 74 of 90 days of AWS learning challenge"
url: "https://hashnode.com/posts/cloudfront-overview-and-cloudfront-with-s3-a-detailed-guide/66c6c443c9ac2057c9a75a92"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [CloudFront Overview and CloudFront with S3: A Detailed Guide](https://shaileshpashte.hashnode.dev/cloudfront-overview-and-cloudfront-with-s3-a-detailed-guide?utm_source=hashnode&utm_medium=feed)

📢 Day 74 of 90 days of AWS learning challenge

Aug 22, 2024 · 5 min read · shaileshpashte.hashnode.dev  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#aws-certified-solutions-architect-associate](https://hashnode.com/tag/aws-certified-solutions-architect-associate)
-   [#aws-cloudfront](https://hashnode.com/tag/aws-cloudfront)
-   [#cdn](https://hashnode.com/tag/cdn)
-   [#contentdeliverynetwork](https://hashnode.com/tag/contentdeliverynetwork)
-   [#cloud-computing](https://hashnode.com/tag/cloud-computing)
-   [#learning](https://hashnode.com/tag/learning)
-   [#learning-journey](https://hashnode.com/tag/learning-journey)
-   [#learning-in-public](https://hashnode.com/tag/learning-in-public)
-   [#90daysofcloud](https://hashnode.com/tag/90daysofcloud)
-   [#90dayslearningchallenge](https://hashnode.com/tag/90dayslearningchallenge)

## Written by

[Shailesh](https://hashnode.com/@shaileshpashte)

@shaileshpashte · Mumbai, India

  
[View profile](https://hashnode.com/@shaileshpashte)

Journey to be Cloud Solution Architect

As a Solution Architect, I am responsible for designing and implementing scalable, secure, and efficient IT solutions. My key responsibilities include: 🔸Analysing business requirements and translating them into technical solutions. 🔸Developing comprehensive architectural plans to meet organizational goals. 🔸Ensuring seamless integration of new technologies with existing systems. 🔸Overseeing the implementation of projects to ensure alignment with design. 🔸Providing technical leadership and guidance to development teams. 🔸Conducting performance assessments and optimizing solutions for efficiency. 🔸Maintaining a keen focus on security, compliance, and best practices. Actively exploring new technologies and continuously refining strategies to drive innovation and excellence.

## Responses 1

Markdown supported · ⌘↵ to post

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Nov 5](https://hashnode.com/posts/cloudfront-overview-and-cloudfront-with-s3-a-detailed-guide/66c6c443c9ac2057c9a75a92/comment/6aec5595cf2826f165801f6a)

Putting S3 behind CloudFront is straightforward; keeping origin request rate down is mostly cache-key and header discipline. Prefer a REST or website origin with an origin access control that only the distribution can call, emit Cache-Control from the object (or a response-headers policy) so edges can store hashed assets long-term, and avoid forwarding the full query string or Cookie on the default behaviour — each unique variant becomes its own object and Origin Shield cannot collapse what the key already split.

Ops prove-out after wiring the origin and cache policy: hit a hashed object twice and expect MISS then HIT with a rising Age, then fetch the HTML shell and confirm it stays on a short TTL or purge tag. After replacing an object in the bucket under the same key, run an invalidation for that path (or rely on versioned filenames) and re-check X-Cache until the old body is gone everywhere that mattered — most “S3 update not visible” tickets are an un-invalidated edge object or a query variant still in the key, not a broken bucket ACL.
