S3 Bucket

Storage Connector – S3 Bucket

The S3 Bucket connector lets you push signed documents, attachments, and completion certificates from emSigner directly into an AWS S3 bucket of your choice, giving you full control over where your signed documents reside.

Navigation: Settings → Storage Connectors for Document Repositories → S3 Bucket tab

Sending Options

Option	Description
Include Signed documents only (selected by default)	Only the signed documents will be pushed to the selected connector.
Include attachments (selected by default)	Attachments will also be included along with the signed documents.
Include completion certificate (optional, not selected by default)	The completion certificate will be included in the connector upload.

Configuration Fields

Field	Description
Bucket Name (required)	The name of the target S3 bucket where documents will be stored.
Access Key (required)	The AWS access key associated with the IAM user/role that has permission to write to the bucket.
Secret Key (required)	The AWS secret key paired with the access key above.
Region (required)	The AWS region where the bucket is hosted (e.g., Asia Pacific (Mumbai)). Select from the dropdown.

Steps to Configure

1. Go to Settings and click on Storage Connectors for Document Repositories.

2. Select the S3 Bucket tab.

3. Review the Sending Options — Include Signed documents only and Include attachments are enabled by default. Optionally, select Include completion certificate if you also want completion certificates pushed to the connector.

4. Enter the Bucket Name, Access Key, Secret Key, and select the Region.

5. Click Generate test file to validate the connection under Step 1: Test Connection.

6. Once the test succeeds, proceed to Step 2: Activate to enable the connector.

Note: Until the connector is activated, documents will continue to follow the existing storage behavior. Once activated, this connector applies at the administrator level — all future signed documents from every user of the application, including internal users, will be pushed to the configured repository (matching the selected Sending Options).