Skip to content

AWS Activities

The AWS Activities Extension Library adds the AWS S3 Upload activity to Integration Soup.

Use it to archive messages, store exports or file content, or hand workflow output to downstream AWS-based processes.

Download

Using it in a workflow

  1. Install the MSI on the Integration Soup server.
  2. Restart the Integration Soup service if needed.
  3. Add AWS S3 Upload after the step that produces the content you want to upload.
  4. In the activity message template, use Insert Activity Message to bring in the content from the receiver or earlier activity.
  5. Fill in the AWS parameter fields below. For reused settings such as credentials or region, insert workflow or global variables.

Parameters

Bucket Name

Enter the destination bucket name, for example integration-archive.

File Name

Enter the S3 object key to create, for example:

  • adt/2026/03/20/ADT_A01_120000.hl7
  • exports/patients/patient-export.json

Region

Enter the AWS region in system-name format, for example:

  • us-west-1
  • ap-southeast-2

Access Key ID

Enter the AWS access key ID used for the upload.

Secret Access Key

Enter the matching secret access key.

Activity message

Place the content you want stored in S3 into the activity message.

The incoming message type is selectable in the workflow designer.

Typical examples:

  • inbound HL7 from a receiver
  • XML or JSON generated by transformers
  • CSV or plain-text output from earlier workflow steps
  • binary file content from an earlier activity
  • DICOM content

Text-based message types are uploaded as UTF-8 bytes. Binary and DICOM messages upload their underlying file bytes.

Response message

The response message is a Text message confirming the upload succeeded.

Typical uses

  • Archiving workflow output to S3
  • Publishing message exports, XML, JSON, or text reports into AWS
  • Storing documents, binary exports, or DICOM files in S3
  • Handing workflow output to downstream systems that already expect data in S3