AWS
Send Seal records to AWS for storage, analysis or further processing.
Put this connection to work Read the platform connection docs
Connect the relevant records to this work in Seal.
Agree the records and transfer direction for this job, then connect the evidence to the work your team needs to review.
AWS
Connected work record
- The selected records and their source references
- Missing or unmatched information
- Next steps for your team to review
What’s connected.
Push critical data from Seal to your AWS environment for archival, analysis, or further processing. Utilize Seal ETL (Data Sync) to automatically transfer records or reports to services like S3, Redshift, or Glacier. Additionally, configure Seal Triggers (using Seal Scripts) to initiate actions in AWS, such as invoking Lambda functions or starting Step Function workflows, based on specific events or data changes within Seal, enabling powerful cross-platform automation.
Connection setup and permissions
Configure event-driven data transfer with Seal ETL. Define the source of record, sync behaviour and handling of missing or duplicate data.
Before it goes live.
Access and write-back
Reading records and writing back are separate decisions. Define which records are in scope, whose permissions apply and which changes require approval.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.