<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>S3 on Adrien Poupa</title>
    <link>https://adrien.poupa.net/tags/s3/</link>
    <description>Recent content in S3 on Adrien Poupa</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 03 Mar 2024 00:00:00 -0500</lastBuildDate>
    <atom:link href="https://adrien.poupa.net/tags/s3/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Serving a S3 Bucket with Kubernetes and Ingress-Nginx</title>
      <link>https://adrien.poupa.net/serving-s3-bucket-kubernetes-ingress-nginx/</link>
      <pubDate>Sun, 03 Mar 2024 00:00:00 -0500</pubDate>
      <guid>https://adrien.poupa.net/serving-s3-bucket-kubernetes-ingress-nginx/</guid>
      <description>The traditional, production-ready way to serve a S3 bucket in production is usually to create a CloudFront distribution, add a S3 origin and configure the desired behaviour.
However, this comes with a small caveat: while you can specify an origin path, this will make CloudFront request the bucket from the path directory, then appending the requested URL.
For example, given the test origin path, example.com/index.html will retrieve s3://bucket-name/test/index.html; example.com/folder/index.html will retrieve s3://bucket-name/test/folder/index.</description>
    </item>
  </channel>
</rss>
