linux-backup-to-s3

Configure encrypted Linux backups to Amazon S3 using restic with restore testing.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/amitkarpe/agent-skills --skill linux-backup-to-s3-amitkarpe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linux-backup-to-s3
Source: https://github.com/amitkarpe/agent-skills/tree/main/skills/linux-backup-to-s3
Command: npx skills add https://github.com/amitkarpe/agent-skills --skill linux-backup-to-s3-amitkarpe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a trustworthy Linux backup to cloud storage involves many moving parts: bucket security, encryption, credentials, retention, and proof that restores actually work. This Skill provides a complete, safety-first workflow for encrypted restic backups to Amazon S3, including the restore tests that make a backup real. ## Core Features & Use Cases - Guided S3 setup: Create or verify buckets with block public access, versioning, server-side encryption, and meaningful tags using AWS CLI profiles. - Restic backup workflow: Initialize an encrypted restic repository, keep secrets out of git under ~/.config/restic/, and run first backups safely without mirror-delete logic. - Restore verification: Run minimum restore tests to a temporary directory and full HDD-break recovery checks for git repos, dotfiles, and config files. - Use Case: After a laptop disk failure, use this Skill's runbook to restore dotfiles, repositories, and Codex guidance from the S3 restic repository onto a fresh disk. ## Quick Start Use the linux-backup-to-s3 skill to set up my encrypted restic backup to S3 and run a restore test.

Frequently Asked Questions about linux-backup-to-s3

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I back up Linux files to Amazon S3 with restic?▼

Install restic, create a password file under ~/.config/restic/ with mode 0600, initialize a repository against your S3 bucket, then run the first backup. Verify with restic snapshots and a small restore test before relying on it.

Restic vs Borg vs Kopia for Linux cloud backup?▼

This workflow prefers restic for Linux-to-S3 backups because it natively supports S3 targets and client-side encryption. Borg or Kopia are only used when explicitly requested by the user.

What S3 bucket settings are required for secure backups?▼

Backup buckets require block public access, versioning enabled, server-side encryption enabled, and meaningful tags. Verify state with s3api get-bucket-versioning, get-public-access-block, get-bucket-encryption, and get-bucket-tagging.

How do I test that my restic backup actually restores?▼

Run restic restore latest --target pointing to a temporary directory, then confirm git repos, dotfiles, and config files are present. A backup is only considered real after at least one restore test succeeds.

Where should restic passwords and AWS credentials be stored?▼

Keep secrets out of git by storing the restic password and env files locally under ~/.config/restic/ with restrictive permissions. Never print restic passwords, AWS keys, or token material in output.