Transmit 5 includes revamped Amazon S3 support for wider compatibility with the latest AWS offerings. These improvements, and some notes about them, are listed below.
New Region Support
The following regions are now supported:
- Hong Kong
- Northern California
- Northern Virginia (Default)
- São Paulo
- US GovCloud West
Support for IAM Roles
Transmit 5.5 introduced support for using AWS IAM roles. More details can be found here.
Increased Maximum File Size Uploading
Transmit 5 now supports uploading files as large as 976GB. To accomplish this, we use multipart uploading automatically for files that are greater than 5GB.
Important Note Regarding Multipart Uploads
If uploading a file greater than 5GB and the upload fails (if your connection is lost, or any other reason) many of the file parts will remain, invisibly, on your S3 bucket and you will be billed for the storage they use until the associated upload is cancelled.
Transmit 5 automatically cancels failed uploads in the case of a disconnect or crash, but we still recommend setting a bucket lifecycle rule which clears these incomplete uploads automatically. Here’s how to do that.
(Note that you will need appropriate S3 account privileges.)
- Go to the S3 page at your AWS console: https://console.aws.amazon.com/s3
- Select your bucket on the left side bucket list, and click “Properties” in the top right to view the bucket’s properties.
- Select “lifecycle”
- Select “Add rule”
- Choose “Whole bucket” when asked for what the rule should target
- Choose “Configure rule”, check the “End and Clean up Incomplete Multipart Uploads” option,
Choose an appropriate length of time to wait for them to complete. (The 7 day default is fine for most people.)
Give your rule a name and then click “Create and Activate Rule”
Storage Class and Encryption Support
You can now set storage classes on your uploaded files, as well as server-side encryption. You can find these settings in the file inspector window/sidebar.
You can learn more about server-side encryption and storage classes on the AWS documentation pages: