Amazon Web Services → Microsoft Azure
Azure equivalent of Amazon S3 Batch Operations
S3 Batch Operations maps most closely to Azure Storage Actions.
About Amazon S3 Batch Operations
| Provider | Amazon Web Services |
|---|---|
| Status | Generally available |
| What it is | Run one operation (copy, tag, restore, invoke Lambda, replicate, and more) across billions of objects from a manifest or inventory report, with tracking and completion reports. |
| Documentation | docs.aws.amazon.com |
| Pricing | Official pricing page |
Azure mappings (1)
| Capability | Azure equivalent | Match |
|---|---|---|
| Bulk operations on billions of objects | Azure Storage Actions | Partial match |
Object tiers, lifecycle & protection(1)
Bulk operations on billions of objects Partial match
S3 Batch Operations maps most closely to Azure Storage Actions. Both are serverless engines that apply an operation to very large object sets. S3 works from a manifest of objects, while Storage Actions evaluates conditions across one or more accounts.
- Selection. S3 Batch Operations works from a CSV manifest, an S3 Inventory report, or a generated manifest. Storage Actions defines conditions (such as name, tags, age, or tier) evaluated against every blob in the assigned accounts.
- Operations. S3 can invoke a Lambda function per object for custom logic. Storage Actions offers a fixed set of operations (such as set tier, tags, immutability, legal hold, and delete).
- Accounts. Storage Actions can target many storage accounts with one task. An S3 Batch Operations job works on one manifest.