Setup and Configuration in Amazon S3 Server Setup in Amazon EC2/Amazon S3 With an Aspera entitlement, HST Server can be installed on an instance in Amazon EC2/Amazon S3 and run as a self-managed, cloud-based server that enables high-speed transfers with your Amazon S3 storage. Using Amazon S3 IAM Roles To avoid setting S3 storage credentials in a transfer user's docroot, you can use your AWS Identity and Access Management (IAM) roles to set docroots to S3 storage. Enabling AWS KMS Encryption for Amazon S3 Cloud Storage AWS Key Management Service (KMS) is an Amazon web service that uses customer master keys to encrypt objects in Amazon S3 cloud storage. You can configure S3 server-side encryption with KMS system-wide or on a user-by-user basis. Setting Amazon S3 Storage Class Options Amazon S3 offers several storage options, including Standard, Standard - Infrequent Access, and Reduced Redundancy Storage. Your Aspera transfer server is configured for Standard storage by default. You can configure your Aspera transfer server to work with other storage classes by editing s3.properties, which sets the default storage class for all transfers to S3. Using Amazon S3 Versioning with Aspera The Amazon S3 bucket version feature enables you to retain multiple versions of an object in the same bucket. By default, Aspera uploads overwrite any object that has the same name as a source file. As of version 3.7.3, Aspera transfers can be configured to work more gracefully with S3 versioning. Managing S3 Content Type Settings When uploading content to AWS S3, the object can be assigned a MIME type that describes the format of the contents. HST Server automatically applies content types to objects uploaded by using FASP transfers, based on a list located in /opt/aspera/etc/trapd/mime-types.props. Enabling Cache-Control in Amazon S3 Use cache-control request headers in Amazon S3 to avoid repeatedly uploading or serving the same files on a per-bucket basis. File Time Stamp Preservation with Object Storage Object storage platforms do not have native support for preserving the modification, access, or creation times of files that are transferred into object storage from traditional file systems. You can configure your Aspera server (version 3.5 or later) and client to preserve the original time stamps on the files and folders when they are transferred in and out of object storage. Time stamps are preserved as metadata associated with the uploaded object, and can be retrieved upon download. Parallel Transfers to Amazon S3 and Amazon EC2 Parallel transfers to cloud storage allow faster uploads by splitting large sets of files across multiple ascp sessions. They are currently supported only for command-line transfers to Amazon S3 and Amazon EC2. Using Trap Links Trap links are small text files that reference a single target object in your Amazon S3 storage. With a Trap link, you can save an object in a different location and with a different name without actually duplicating the object. For use cases, see the examples following the configuration instructions. Disabling the Creation of 0 Byte Folder Objects in Amazon S3 Storage on Upload When you upload files located in folders to S3 storage, Aspera creates a 0 byte folder object to represent the folder. These objects enable Aspera clients, such as IBM Aspera Desktop Client and IBM Aspera Shares, to represent the folders in their user interfaces. If you programmatically upload many (millions) of objects and folders to S3 storage, disabling this feature decreases the number of objects that are created.