Amazon S3
Connect Amazon Simple Storage Service to Kizen to work with live S3 data in real time. Build Agentic Workflows to upload Kizen files to S3 buckets, copy files, retrieve file lists, and more.
Audience: Admins, Developers, Solution Architects
Purpose: Explains what the Amazon S3 integration is, when to use it, and how it works within your Agentic Workflows
Overview
Connect Amazon Simple Storage Service (S3) to Kizen with the Amazon S3 integration. Upload Kizen files to S3 buckets, copy files and file content between Kizen and S3, retrieve lists of files, and create temporary presigned upload and download URLs, all from your Agentic Workflows in Kizen.
What Is the Amazon S3 Integration?
The Amazon S3 integration adds six action steps to the Agentic Workflow builder:
Upload File: Uploads a Kizen file to Amazon S3
Get File Content: Creates an identical file in Kizen from an S3 file
Get File Metadata: Returns information about an S3 file
List Files: Returns a list of S3 files by folder
Copy File: Creates a server-side copy of an S3 file
Generate Presigned URL: Creates an upload or download URL for S3 storage or retrieval
You configure the connection to Amazon S3 once, as an integration secret in Kizen. See Set Up Amazon S3 in Kizen for details.
The integration supports a single S3 environment or multiple environments, each with its own connection credentials. You specify which to use when you call an S3 action from your Agentic Workflow. To learn more, see Work with Amazon S3 Files in an Agentic Workflow.
When to Use the Amazon S3 Integration
Use the Amazon S3 integration when you want to build Agentic Workflows to access your S3 files and storage.
If your team's documents, exports, media, or compliance records reside in their own S3 buckets and you want to be able to write to these buckets automatically, without the need for custom integration code and without giving individual users direct access to your Amazon Web Services account, this integration can help.
Common Use Cases
Here are some common use cases of the Amazon S3 integration:
Archiving a signed loan package to the lender's S3 bucket at closing
Pulling a newly received referral into the patient record for automated intake
Sending a claimant a secure link to upload damage photos directly to an S3 bucket
How the Amazon S3 Integration Works
Before you configure the Amazon S3 integration, it's important to understand how it functions at a conceptual level.
Connection Model
Connecting to Amazon S3 from Kizen requires an Amazon Web Services (AWS) account with at least one S3 bucket. During integration setup, you create an IAM user for the integration in your AWS account and attach an IAM policy to this user, which governs what the integration can do with your S3 files and how it can use your storage space. Because the integration doesn't utilize an authorization protocol like OAuth, you must also create an AWS access key for this user, which grants them access the designated files and buckets.
Kizen keeps your connection credentials to Amazon S3 as an integration secret. The same secret can hold the credentials for multiple S3 environments, such as production and archive. Specify the environment in which to work at each S3 step of the Agentic Workflow.
For more information, see Set Up Amazon S3 in Kizen.
Authentication
Your AWS access key doesn't normally require reauthorization. However, if you rotate or revoke the key manually, S3 actions in Kizen fail with an invalid access key error. To reauthorize, supply a new access key.
Account Type
A standard AWS account is sufficient to use the integration. You don't need a special membership tier.
Network
No additional network configuration is required to use the integration. You don't need to set your firewall to allow inbound TCP traffic from a specific port, and you don't need to add Kizen's egress IP address to any AWS allowlist. Access is governed entirely through your PAT and Unity Catalog permission grants.
Input Handling
The Upload File action takes as an optional input the API name of the Amazon S3 storage class of the file to upload. For a complete list of S3 storage classes and their API names, see the Amazon Simple Storage Service documentation.
Output Handling
The List Files action returns a stringified JSON array, not a native array. Parse the results with a JSON Parse step in the Agentic Workflow before use.
The action also has a hard limit of 50,000 characters per result. If a list of files would exceed this limit, the step fails without returning any of the files on the list. To avoid this error, target the query with the action's filters. See Troubleshoot Amazon S3 for more information.
Error Handling
If an S3 step of an Agentic Workflow fails, the integration waits a short time and makes a second attempt. If the second attempt fails, the Agentic Workflow fails.
How to Use the Amazon S3 Integration
For step-by-step instructions on using the Amazon S3 integration, see the following topics:
What's Next
Continue to Set Up Amazon S3 in Kizen to configure the connection.
Amazon Web Services, AWS, Amazon Simple Storage Service, and Amazon S3 are trademarks of Amazon.com, Inc. or its affiliates. Kizen's Amazon S3 integration is not affiliated with, sponsored by, or endorsed by Amazon.com, Inc.
Last updated
Was this helpful?