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.
Markdown supported · ⌘↵ to post
CDN Edge Ops
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.