AWS Cloud Connector S3 Setup
Configure S3 buckets, IAM permissions, and lifecycle controls for the Trusted Signatures AWS Cloud Connector.
- Source and destination buckets
- Bucket policies
- Lifecycle cleanup
AWS proof
Use Lambda and S3 for connector speed, scale, and account-scoped control
The documented AWS pattern uses Lambda for invocation, S3 for document movement, and AWS-native IAM and secrets controls so teams can run sealing workflows inside their own account.
S3
speed path
Source and destination buckets let applications hand off PDFs and retrieve sealed output through the same storage workflow.
Lambda
scale model
The connector runs as a Lambda function, fitting bursty or event-driven document jobs without managing long-lived servers.
IAM
security controls
Least-privilege roles, bucket policies, and Secrets Manager guidance scope access to documents and credentials.
SHA-256
data boundary
Only the document digest and signing metadata are sent to Trusted Signatures while PDFs stay in S3.
S3 Setup Guide
Overview
The AWS Cloud Connector uses S3 buckets to handle PDFs of any size. You need to configure S3 buckets and permissions before using the connector.
S3 Bucket Setup
Create Buckets
You need at least one S3 bucket (can use the same bucket for source and destination):
| |
Bucket Policy (Optional)
Restrict access to your buckets:
| |
Lambda IAM Permissions
Update your Lambda execution role with S3 permissions:
| |
Usage Workflow
1. Upload PDF to S3
| |
2. Invoke Lambda
| |
3. Download Sealed PDF
| |
Presigned URLs (Optional)
For secure uploads without AWS credentials:
| |
Security Best Practices
Bucket Encryption
Enable server-side encryption:
| |
Lifecycle Policies
Automatically delete temporary files:
| |
Access Logging
Enable access logging for audit:
| |
Troubleshooting
Access Denied Errors
- Verify Lambda execution role has correct S3 permissions
- Check bucket policies don’t block Lambda access
- Ensure bucket and object exist
Large File Timeouts
- Increase Lambda timeout (max 15 minutes)
- Consider Lambda memory allocation for large files
- Monitor CloudWatch metrics
Cost Optimization
- Use S3 Intelligent Tiering for infrequent access
- Set up lifecycle policies to delete temporary files
- Consider S3 Transfer Acceleration for large uploads
Monitoring
CloudWatch Metrics
Monitor S3 usage:
- NumberOfObjects
- BucketSizeBytes
- AllRequests
Cost Tracking
- Enable S3 cost allocation tags
- Monitor data transfer costs
- Track storage costs by bucket
Need architectural review?
Book a technical walkthrough
For enterprise rollout, we can review trust model, controls, and integration patterns with your team.