S3

What Goal: Mount an AWS S3 bucket as a Windows drive letter (e.g., S:) using rclone. Scope: One S3 remote via rclone config, one batch file to mount, optional auto‑start. Prerequisites: AWS account + S3 bucket + IAM user with access to that bucket. rclone for Windows. WinFSP (required for rclone mount on Windows). Why Faster access: Browse S3 in File Explorer without separate apps or consoles. Simplicity: Open, copy, rename like a normal drive letter. Integrations: Any Windows app that works with drive letters can work with S3. How Step 1 — Install rclone + WinFSP ...

What Goal: Back up Android photos/media privately to AWS S3 using FolderSync (Android). Scope: One S3 bucket, one IAM user, FolderSync account (S3-compatible), one folder pair (2‑way sync). Prerequisite: AWS account ready. Why Own your data: No Big Tech gallery lock-in. Reliability: S3 durability + Intelligent‑Tiering for cost control. Simplicity: No self‑hosted NAS, static IP, RAID, or server maintenance. How Step 1 — Create S3 bucket (Region: us‑east‑1 recommended) Name: your choice (e.g., mobile-device-bkp). Region: us-east-1 (often lowest cost; change if you need locality). Block Public Access: ON (keep the bucket private). Versioning: optional but recommended for safety. Storage class: add a lifecycle rule to transition objects to Intelligent‑Tiering immediately. Step 2 — Create IAM policy (access only this bucket) ...

Series links: Part 1/5 – Introduction Part 2/5 – Database Planning Part 3/5 – AWS Setup (you are here) Part 4/5 – Backend APIs Part 5/5 – Frontend What A light AWS setup to hold two things: your files (bills) and your data (transactions). Why S3 is reliable and affordable for documents/photos. RDS PostgreSQL gives you a managed database without running servers. How S3 bucket for web hosting (public read) Create a bucket for the static site (e.g., my-expenses-web). Make it public-read so the HTML/CSS/JS can be fetched by browsers. Optionally use CloudFront in front; with OAC you can keep the bucket private and still serve publicly via the CDN. Alternative hosts: Netlify, Vercel, or any simple web server. S3 bucket for documents (private) ...

What You can deploy the hugo project to s3 directly when you make a push to github repository. this is a guide for that. you are going to use AWS s3, IAM role with s3 access and cloudfront access if you want to use cloudfront in front of s3 bucket. How the github action for your repo will be name: Deploy to S3 on: push: branches: - master jobs: deploy: runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v4 with: submodules: true - name: Set up Hugo uses: peaceiris/actions-hugo@v3 with: hugo-version: 'latest' - name: Build the Hugo site run: hugo --verbose --debug - name: Sync S3 bucket uses: jakejarvis/s3-sync-action@master with: args: --delete env: AWS_S3_BUCKET: your-bucket AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} AWS_REGION: 'us-west-1' SOURCE_DIR: 'public' - name: Invalidate CloudFront uses: chetan/invalidate-cloudfront-action@v2 env: DISTRIBUTION: YOUR-CF-DIST-ID PATHS: "/*" AWS_REGION: "us-east-1" AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} If you are not using and CF, ignore the cloudfront invalidation part. and you are good to go.