[{"_1":2,"_183":-5,"_184":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_162":163},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":89,"_112":113,"_151":-5,"_152":11,"_153":21,"_154":11,"_155":-5,"_156":11,"_157":-5,"_158":159,"_160":114,"_161":-7},"canonicalUrl","https://hub.docker.com/r/caesarteam/backuper/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","caesarteam","reponame","backuper","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2020-12-08T17:29:26.886994Z","description","aws-database-backup is a container image based on Alpine Linux.","is_private","last_updated","2020-12-08T19:07:22.541326Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",380,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# aws-database-backup\n\naws-database-backup is a container image based on Alpine Linux. This container is designed to run in Kubernetes as a cronjob to perform automatic backups of MySQL/PostgreSQL databases to Amazon S3. It was created to meet my requirements for regular and automatic database backups. Having started with a relatively basic feature set, it is gradually growing to add more and more features.\n\nCurrently, aws-database-backup supports the backing up of MySQL/PostgreSQL Databases. It can perform backups of multiple MySQL/PostgreSQL databases from a single database host. When triggered, a full database dump is performed using the `mysqldump` or `pg_dump` command for each configured database. The backup(s) are then uploaded to an Amazon S3 Bucket. aws-database-backup features Slack Integration, and can post messages into a channel detailing if the backup(s) were successful or not.\n\nOver time, aws-database-backup will be updated to support more features and functionality. I currently use this container as part of my Kubernetes Architecture which you can read about [here](https://benjamin.maynard.io/this-blog-now-runs-on-kubernetes-heres-the-architecture/).\n\nAll changes are captured in the [changelog](CHANGELOG.md), which adheres to [Semantic Versioning](https://semver.org/spec/vadheres2.0.0.html).\n\n\n## Environment Variables\n\nThe below table lists all of the Environment Variables that are configurable for aws-database-backup.\n\n| Environment Variable | Purpose |\n| --------------------------- |------------------------------------------------------------------------------------------------------------------|\n| AWS_ACCESS_KEY_ID | **(Required)** AWS IAM Access Key ID. |\n| AWS_SECRET_ACCESS_KEY | **(Required)** AWS IAM Secret Access Key. Should have very limited IAM permissions (see below for example) and should be configured using a Secret in Kubernetes. |\n| AWS_DEFAULT_REGION | **(Required)** Region of the S3 Bucket (e.g. eu-west-2). |\n| AWS_BUCKET_NAME | **(Required)** The name of the S3 bucket. |\n| AWS_BUCKET_BACKUP_PATH | **(Required)** Path the backup file should be saved to in S3. E.g. `/database/myblog/backups`. **Do not put a trailing / or specify the filename.** |\n| DB_HOST | **(Required)** Hostname or IP address of the database Host. |\n| DB_PORT | **(Optional)** Port of the database is listening on (Default: 3306 (mysql) and 5432 (pgsql)). |\n| TARGET_DATABASE_NAMES | **(Required)** Name of the databases to dump. This should be comma seperated (e.g. `database1,database2`). |\n| DB_USER | **(Required)** Username to authenticate to the database with. |\n| DB_PASSWORD | **(Required)** Password to authenticate to the database with. Should be configured using a Secret in Kubernetes. |\n| ENCRYPT | **(Optional)** The backup will encrypt with the command `openssl enc -aes-256-cbc -salt`. Should be configured using a config in Kubernetes. |\n| ENCRYPT_PASS | **(Optional)** The password for encryption the database. Should be configured using a Secret in Kubernetes. |\n| SLACK_ENABLED | **(Optional)** (true/false) Enable or disable the Slack Integration (Default False). |\n| SLACK_USERNAME | **(Optional)** (true/false) Username to use for the Slack Integration (Default: aws-database-backup). |\n| SLACK_CHANNEL | **(Required if Slack enabled)** Slack Channel the WebHook is configured for. |\n| SLACK_WEBHOOK_URL | **(Required if Slack enabled)** What is the Slack WebHook URL to post to? Should be configured using a Secret in Kubernetes. |\n\n\n## Slack Integration\n\naws-database-backup supports posting into Slack after each backup job completes. The message posted into the Slack Channel varies as detailed below:\n\n* If the backup job is **SUCCESSFUL**: A generic message will be posted into the Slack Channel detailing that all database backups successfully completed.\n* If the backup job is **UNSUCCESSFUL**: A message will be posted into the Slack Channel with a detailed error message for each database that failed.\n\nIn order to configure aws-database-backup to post messages into Slack, you need to create an [Incoming WebHook](https://api.slack.com/incoming-webhooks). Once generated, you can configure aws-database-backup using the environment variables detailed above.\n\n## Configuring the S3 Bucket & AWS IAM User\n\naws-database-backup performs a backup to the same path, with the same filename each time it runs. It therefore assumes that you have Versioning enabled on your S3 Bucket. A typical setup would involve S3 Versioning, with a Lifecycle Policy.\n\nAn IAM Users should be created, with API Credentials. An example Policy to attach to the IAM User (for a minimal permissions set) is as follows:\n\n```\n{\n \"Version\": \"2012-10-17\",\n \"Statement\": [\n {\n \"Sid\": \"VisualEditor0\",\n \"Effect\": \"Allow\",\n \"Action\": \"s3:ListBucket\",\n \"Resource\": \"arn:aws:s3:::\"\n },\n {\n \"Sid\": \"VisualEditor1\",\n \"Effect\": \"Allow\",\n \"Action\": [\n \"s3:PutObject\"\n ],\n \"Resource\": \"arn:aws:s3:::/*\"\n }\n ]\n}\n```\n\n\n## Example Kubernetes Cronjob\n\nAn example of how to schedule this container in Kubernetes as a cronjob is below. This would configure a database backup to run each day at 01:00am. The AWS Secret Access Key, and Target Database Password are stored in secrets.\n\n```\napiVersion: v1\nkind: Secret\nmetadata:\n name: AWS_SECRET_ACCESS_KEY\ntype: Opaque\ndata:\n aws_secret_access_key: \n--\napiVersion: v1\nkind: Secret\nmetadata:\n name: TARGET_DATABASE_PASSWORD\ntype: Opaque\ndata:\n database_password: \n--\napiVersion: v1\nkind: Secret\nmetadata:\n name: SLACK_WEBHOOK_URL\ntype: Opaque\ndata:\n slack_webhook_url: \n--\napiVersion: batch/v1beta1\nkind: CronJob\nmetadata:\n name: my-database-backup\nspec:\n schedule: \"0 01 * * *\"\n jobTemplate:\n spec:\n template:\n spec:\n containers:\n - name: my-database-backup\n image: benjaminmaynard/aws-database-backup\n imagePullPolicy: Always\n env:\n - name: AWS_ACCESS_KEY_ID\n value: \"\"\n - name: AWS_SECRET_ACCESS_KEY\n valueFrom:\n secretKeyRef:\n name: AWS_SECRET_ACCESS_KEY\n key: aws_secret_access_key\n - name: AWS_DEFAULT_REGION\n value: \"\"\n - name: AWS_BUCKET_NAME\n value: \"\"\n - name: AWS_BUCKET_BACKUP_PATH\n value: \"\"\n - name: DB_HOST\n value: \"\"\n - name: DB_PORT\n value: \"\"\n - name: TARGET_DATABASE_NAMES\n value: \"\"\n - name: DB_USER\n value: \"\"\n - name: DB_PASSWORD\n valueFrom:\n secretKeyRef:\n name: DB_PASSWORD\n key: database_password\n - name: SLACK_ENABLED\n value: \"\"\n - name: SLACK_CHANNEL\n value: \"#chatops\"\n - name: SLACK_WEBHOOK_URL\n valueFrom:\n secretKeyRef:\n name: SLACK_WEBHOOK_URL\n key: slack_webhook_url\n restartPolicy: Never\n```\n","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",368102662,"orgData",{"_90":91,"_92":93,"_94":95,"_96":33,"_97":98,"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":104,"_110":104,"_111":21},"id","ed73e8d944d449419aef780bc6d0bd00","uuid","ed73e8d9-44d4-4941-9aef-780bc6d0bd00","type","organization","orgname","full_name","Caesar.Team","location","London, UK","company","Caesar","profile_url","","date_joined","2018-10-28T12:44:40.971931Z","gravatar_url","https://www.gravatar.com/avatar/02ff10dee0143ddf5b7769c2e5b10e20?s=80&r=g&d=mm","gravatar_email","badge","is_active","recentTags",[114],{"_115":44,"_116":117,"_118":119,"_90":120,"_121":122,"_50":139,"_140":141,"_142":33,"_143":56,"_57":144,"_145":146,"_147":130,"_148":139,"_149":66,"_150":21},"content_type","creator",259659,"full_size",105149205,129200888,"images",[123],{"_124":125,"_126":127,"_128":104,"_129":130,"_131":132,"_133":134,"_135":104,"_136":-5,"_137":119,"_63":66,"_138":-5},"architecture","amd64","digest","sha256:cbcf94f8f0119c46849848eddf7355c6d5529189f364111ce69b29d4c0500196","features","last_pulled","2026-10-12T06:21:36.559555603Z","last_pushed","2020-12-08T19:07:20Z","os","linux","os_features","os_version","size","variant","2020-12-08T19:07:19.943668Z","last_updater",4441177,"last_updater_username","media_type","latest","repository",10392209,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":164,"_171":172,"_158":181,"_182":11},{"_40":165,"_42":166,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":167,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":168,"_79":11,"_80":170,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":169},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_173":64,"_174":-5,"_175":-5,"_176":177},"count","next","previous","results",[178],{"_115":44,"_116":117,"_118":119,"_90":120,"_121":179,"_50":139,"_140":141,"_142":33,"_143":56,"_57":144,"_145":146,"_147":130,"_148":139,"_149":66,"_150":21},[180],{"_124":125,"_126":127,"_128":104,"_129":130,"_131":132,"_133":134,"_135":104,"_136":-5,"_137":119,"_63":66,"_138":-5},[],"canDeleteTags","actionData","errors"]

caesarteam/backuper

Tags for caesarteam/backuper