PROCESIO
OverviewPlatform ActionsIntegrations & DemosMarketplaceCustom ActionsDeveloperโ€™s Guide

Delete by Keys

Deletes a list of objects from an Amazon S3 bucket in one request.

Delete by Keys removes several objects from an Amazon S3 bucket in one step. You give the list of keys, for example the result of List Keys after you filtered it.

Before you start

The AWS S3 actions don't use a stored credential. Each action has the same four connection fields:

FieldTypeRequiredWhat to put
Access KeyTextYesThe access key ID of an AWS IAM user, for example AKIAโ€ฆ.
Secret KeyTextYesThe secret access key that belongs to that access key.
RegionTextYesThe AWS region of the bucket, as its code, for example eu-central-1.
BucketTextYesThe bucket name, for example my-company-invoices.

The IAM user needs S3 permissions on the bucket for the operation you run. The values you type are visible to everyone who can edit the process, so prefer an IAM user limited to the buckets the process needs.

Add the action

In the Process Designer toolbox, open AWS S3 and pick Delete by Keys (or type Delete by Keys in the search box).

The Delete by Keys action properties: Access Key, Secret Key, Region, Bucket, Keys and Result

Inputs and outputs

FieldDirectionTypeRequiredWhat to put / what you get
Access Key, Secret Key, Region, BucketInputTextYesThe connection fields described above.
KeysInputList of TextYesThe full keys of the objects to delete, for example ["reports/2024.csv", "reports/2025.csv"].
ResultOutputBooleanNotrue if the request succeeded, false if not.

Example

Keys ["reports/2024.csv", "reports/2025.csv"] โ†’ both objects are removed and Result is true.

Good to know

  • An empty list returns Result false without deleting anything. If Keys isn't set at all, the step fails with "Missing keys."
  • S3 doesn't report keys that don't exist, so Result can be true even when some keys were already gone.
  • S3 accepts at most 1,000 keys in one request. Split longer lists.
  • The deletion can't be undone.
  • If a connection field is empty, the step fails with "Invalid connection details."
  • Common errors from S3: "Access forbidden! Ensure the connection details are valid." (wrong keys or missing permission), "Unable to connect! Ensure the provided region matches the bucket one." (wrong Region), and "Unrecognized Amazon Region: โ€ฆ" (a region code that doesn't exist).

On this page