Save every generated PDF to your own S3 bucket
DocSpring can copy every PDF it generates into an Amazon S3 bucket you own. Organize the files your way and keep a complete archive in your AWS account.
What you can do with AWS S3
Uploads
- Every PDF, automatically
- Each PDF is uploaded as soon as it's generated, including combined PDFs.
- Your own file paths
- Build each path from the template, the date, and your own metadata, for example a folder for each client.
- Choose which PDFs
- Upload live PDFs, test PDFs or both, and limit uploads to specific API tokens.
Access and status
- Write-only IAM role
- Give DocSpring a role that can only add files to your bucket, or use an access key.
- Upload status
- Each PDF shows whether its upload is pending, done, or failed, with the reason for any failure.
Set up the AWS S3 integration
- In DocSpring, open Integrations and choose Manage S3 connections.
- Create an S3 integration with your bucket's name and its AWS region.
- Create an IAM role that DocSpring can assume with permission to add files to that bucket, or enter an access key.
- Set the file path and choose which PDFs to upload.
- Generate a PDF and check that it appears in your bucket.
Example workflows
An archive you control
Keep a copy of every generated and signed document in your own account, under your own retention rules.
Start your own processing
Use S3 event notifications to run a Lambda function or another workflow when a new PDF arrives.
Separate environments
Send PDFs from your staging and production API tokens to different buckets.
More integrations
Try DocSpring with AWS S3
Upload a PDF or create an HTML template, then connect AWS S3. No credit card required.