Expose file storage without building or hosting it
Let customers store, retrieve, and archive files in their own S3 accounts while your…
Amazon S3 Integrations
Help you with Backup, Archive, Big Data Analytics, Disaster Recovery, and much more.
Event-driven workflows and automation
Use S3 event notifications together with Cyclr orchestration to trigger processing, notifications, or downstream…
Multi-tenant safe, governed integrations
Package S3 operations as governed MCP tools so customers get consistent, permissioned access to…
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Create automations with our Amazon S3 connector
Cyclr enables SaaS platforms to integrate their application with hundreds of other platforms. Use Cyclr’s low code integration builder to integrate your application with Amazon S3, so you can provide in-app Amazon S3 integrations for your end users.
PRODUCT USE CASES
Top Use Cases for Amazon S3 Integrations
Quickly create integrations between your SaaS application and Amazon S3 with Cyclr’s low code integration builder. Publish your Amazon S3 integration into your application using Cyclr’s white label embedded integration marketplace.
Tenant-managed backups to customers' S3 buckets
Allow each customer to point to their own S3 bucket for automated backups and archives. Use Cyclr to orchestrate scheduled uploads, verify completion, and surface status in your app.
In-app file storage and presigned uploads
Enable direct browser or client uploads via presigned URLs generated from customer credentials so files land in the customer’s S3 account without routing large payloads through your servers.
Automate post-upload workflows
When a customer uploads objects to S3, use S3 event notifications (SNS, SQS, Lambda or EventBridge) to trigger Cyclr workflows that transcode, index, or sync those files into downstream services.
ORCHESTRATION
How Amazon S3 works with Cyclr
Cyclr sits between your SaaS product and Amazon S3 to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Amazon S3
Amazon S3 processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Amazon S3 methods you can orchestrate through Cyclr.
Objects13
Get JSON Object
ActionGet a JSON object from a bucket.
Get XML Object
ActionGet an XML object from a bucket.
Add JSON Object (Entire Response)
ActionAdd a JSON object using the entire response of a previous step to a bucket.
Add Extended Object
ActionAdd an extended object to a bucket.
List Objects
ActionList all objects in a bucket.
Get Object
ActionGet an object from a bucket.
Add Object
ActionAdd an object to a bucket.
List Updated Objects
ActionList all objects in a bucket created or updated since the last successful run.
Get CSV Object
ActionGet a CSV object from a bucket.
Add JSON Object
ActionAdd a JSON object to a bucket.
Add JSON Object (Mapped Fields)
ActionAdd a JSON object with mapped fields to a bucket.
Delete Object
ActionDelete an object from a bucket.
Add XML Object
ActionAdd an XML object to a bucket.
Buckets4
Create Bucket
ActionCreate a bucket.
List New Buckets
ActionList all buckets created since the last successful run.
List Buckets
ActionList all buckets.
Delete Bucket
ActionDelete a bucket.
TECHNICAL DETAILS
Amazon S3 integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Amazon S3 integrations in Cyclr.
API and authentication
- API host
Amazon S3 uses region-specific endpoints and supports virtual-hosted–style and path-style addressing (for example virtual-hosted: {bucket}.s3.{region}.amazonaws.com; path-style: s3.{region}.amazonaws.com).- Authentication
- AWS access key and secret access key using AWS Signature Version 4 (supports optional session token)
- Credentials
Required fields typically include AWS Access Key ID, AWS Secret Access Key, and AWS Region. Optional fields or advanced setups may include a session…
- Method categories
Common method categories include bucket management (CreateBucket, DeleteBucket, ListBuckets), object management (PutObject, GetObject, DeleteObject, CopyObject, HeadObject, multipart upload operations), listings and pagination (ListObjectsV2), access…
Pagination and rate limits
Pagination
Object listing uses ListObjectsV2 with continuation tokens. Results are returned in pages and clients use the NextContinuationToken or ContinuationToken to paginate; default/max page sizes are controlled by the max-keys parameter (ListObjects/ListObjectsV2).
Rate limits
Amazon S3 does not publish a single global request quota. AWS guidance and performance best practices show S3 can support thousands of requests per second and provide example guidance such as at least 3,500 PUT/COPY/POST/DELETE…
IMPLEMENTATION
Authentication at a glance
Authenticate using an IAM access key ID and secret access key. Requests to S3 must be signed with AWS Signature Version 4; SDKs and the REST API both use this signing method. Temporary credentials such as session tokens from STS are also supported where needed.
- Authentication method
- AWS access key and secret access key using AWS Signature Version 4 (supports optional session token)
- Credential required
Required fields typically include AWS Access Key ID, AWS Secret Access Key, and AWS Region. Optional fields or advanced setups may include a session…
Before you begin:
View setup guideCyclr’s connector setup requires an IAM access key and secret key with correct permissions. Cyclr documentation notes a limitation: bucket names containing a period…
COMMON QUESTIONS
Frequently asked questions
You supply an IAM access key ID and secret access key. Requests must be signed using AWS Signature Version 4. Temporary credentials from STS (session token) are supported where required. Be sure the IAM principal has the permissions your integration needs (for example s3:PutObject s3:GetObject s3:ListBucket).
Amazon S3 supports event notifications that can target SNS SQS Lambda or EventBridge. You can connect those destinations into your orchestration to build webhook-style flows or trigger processing pipelines; if you need HTTP delivery you can use SNS HTTP/HTTPS endpoints or an intermediary that converts messages into webhooks.
AWS does not publish a single global limit for S3 but provides performance guidance. Under recommended patterns S3 can handle thousands of requests per second; AWS guidance gives example rates such as at least 3,500 PUT/COPY/POST/DELETE and 5,500 GET/HEAD requests per second per prefix. Design your integration to use retries and exponential backoff for transient throttling.
Common actions you can map and expose include ListObjects (with pagination), GetObject, PutObject, DeleteObject, CreateBucket, and generating presigned URLs. Package these actions as governed MCP tools so customers only get the operations and permissions you want to expose and you can monitor usage centrally.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorMicrosoft SQL Server
Related Databases connector for customer-facing integration workflows.
Related connectorMicrosoft SQL Server - Table
Related Databases connector for customer-facing integration workflows.
Related connectorDataDog
Related Analytics connector for customer-facing integration workflows.