<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on Jhuk Tech News</title><link>https://jhuk.tech/tags/docker/</link><description>Recent content in Docker on Jhuk Tech News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 30 Jun 2026 00:30:00 +0000</lastBuildDate><atom:link href="https://jhuk.tech/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Splunk Enterprise on AWS: Architecting EC2, Docker, IAM, and SNS/SQS Log Ingestion Pipeline</title><link>https://jhuk.tech/2026/06/30/splunk-enterprise-on-aws/</link><pubDate>Tue, 30 Jun 2026 00:30:00 +0000</pubDate><guid>https://jhuk.tech/2026/06/30/splunk-enterprise-on-aws/</guid><description>&lt;p&gt;My blog runs as a static S3 origin behind CloudFront, deployed by Terraform and GitHub Actions. The edge was producing access logs, but they were sitting inert in object storage. I could not yet answer questions and produce intelligence like: Who is requesting what? Why are certain clients requesting paths or filenames that result in 403 or 404? How often does CloudFront serve from cache versus reaching back to S3?&lt;/p&gt;</description></item></channel></rss>