Skip to main content

Automated AWS S3 / Azure / Google to local MinIO object backup with scheduling

Workflow preview

Workflow preview
100%
Automated AWS S3 / Azure / Google to local MinIO object backup with scheduling preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Automated AWS S3 / Azure / Google to local MinIO Object Backup with Scheduling What this workflow does ? This workflow performs automated, periodic backups of objects from an AWS S3 bucket, an Azur...

Best for

  • File Management automation workflows
  • Multimodal AI automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.splitout, n8n-nodes-base.scheduletrigger, n8n-nodes-base.awss3, n8n-nodes-base.s3, n8n-nodes-base.azurestorage, n8n-nodes-base.googlecloudstorage

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by SIENNA.

Original n8n.io source

1.1 Workflow description

Title
Automated AWS S3 / Azure / Google to local MinIO object backup with scheduling
Workflow name
Automated AWS S3 / Azure / Google to local MinIO object backup with scheduling

Automated AWS S3 / Azure / Google to local MinIO Object Backup with Scheduling

What this workflow does ?

This workflow performs automated, periodic backups of objects from an AWS S3 bucket, an Azure Container or a Google Storage Space to a MinIO S3 bucket running locally or on a dedicated container/VM/server. It can also work if the MinIO bucket is running on a remote cloud provider's infrastructure; you just need to change the URL and keys.

Who's this intended for ?

Storage administrators, cloud architects, or DevOps who need a simple and scalable solution for retrieving data from AWS, Azure or GCP.

How it works

This workflow uses the official AWS S3 API to list and download objects from a specific bucket, or the Azure BLOB one, then send them to MinIO using their version of the S3 API.

Requirements

None, just a source Bucket on your Cloud Storage Provider and a destination one on MinIO. You'll also need to get MinIO running.

You're using Proxmox VE ? Create a MinIO LXC Container : https://community-scripts.github.io/ProxmoxVE/scripts?id=minio

Need a Backup from another Cloud Storage Provider ?

Need automated backup from another Cloud Storage Provider ?

$\mapsto$ Check out our templates, we've done it with AWS, Azure, and GCP, and we even have a version for FTP/SFTP servers!

For a dedicated source Cloud Storage Provider, please contact us !

$\odot$ These workflow can be integrated to bigger ones and modified to best suit your needs ! You can, for example, replace the MinIO node to another S3 Bucket from another Cloud Storage Provider (Backblaze, Wasabi, Scaleway, OVH, ...)

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note37

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Path Extraction

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 3 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 4 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - List Objects

Type / Role
n8n-nodes-base.awsS3 - awsS3
Config choices
Version 2

Block 7 - Download Objects

Type / Role
n8n-nodes-base.awsS3 - awsS3
Config choices
Version 2

Block 8 - Upload Objects to MinIO

Type / Role
n8n-nodes-base.s3 - s3
Config choices
Version 1

Block 9 - BLOB Listing

Type / Role
n8n-nodes-base.azureStorage - azureStorage
Config choices
Version 1

Block 10 - Path extraction

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 11 - BLOB Download

Type / Role
n8n-nodes-base.azureStorage - azureStorage
Config choices
Version 1

Block 12 - MinIO BLOB Upload

Type / Role
n8n-nodes-base.s3 - s3
Config choices
Version 1

Block 13 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Object Listing

Type / Role
n8n-nodes-base.googleCloudStorage - googleCloudStorage
Config choices
Version 1

Block 15 - Upload on MinIO

Type / Role
n8n-nodes-base.s3 - s3
Config choices
Version 1

Block 16 - Download Objects Data

Type / Role
n8n-nodes-base.googleCloudStorage - googleCloudStorage
Config choices
Version 1

Block 17 - Path extraction1

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 18 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Automated AWS S3 / Azure / Google to local MinIO object backup with scheduling
Complexity advanced
Nodes 19
Categories File Management, Multimodal AI
Author SIENNA
Published 12 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7284/7284.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automated AWS S3 / Azure / Google to local MinIO object backup with scheduling do?

Automated AWS S3 / Azure / Google to local MinIO Object Backup with Scheduling What this workflow does ? This workflow performs automated, periodic backups of objects from an AWS S3 bucket, an Azur...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management, Multimodal AI use case.