Setup and configuration in Amazon S3 Server setup in Amazon EC2 and Amazon S3An Aspera® server can be deployed on an instance in Amazon EC2 and Amazon S3 and run as a self-managed, cloud-based server that supports high-speed transfers with your Amazon S3 storage and by having an Aspera® license or consumption-based entitlement.Using Amazon S3 IAM rolesTo 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 storageAWS 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 optionsAmazon S3 offers several storage options, including Standard, S3 Standard-Infrequent Access (S3 Standard-IA), 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 AsperaThe Amazon S3 bucket version feature gives you the option 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. Managing S3 content type settingsWhen uploading content to AWS S3, the object can be assigned a MIME type that describes the format of the contents. HSTS 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 S3Use cache-control request headers in Amazon S3 to avoid repeatedly uploading or serving the same files on a per-bucket basis.File timestamp preservation with object storageObject 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 and client to preserve the original timestamps 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 EC2Parallel 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 linksTrap 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 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 UploadWhen you upload files that are 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.Parent topic: Setting up Trapd and Object Storage