New in 2.2: S3 Direct Upload Capability

Implementing direct storage of .tap and .tap.sig output files into AWS S3 with configurable storage tiers is a desirable goal. This is made easier by the existence of the boto3 library, which is maintained by Amazon for the purpose of integrating with AWS and will significantly lower the labour cost of implementation.

Users should be able to specify from within the tapestry.cfg whether or not to use S3 storage as well as a storage tier. Storage tiers, particularly, should be configurable to be different for default and --inc runs of the application.

Delay the implementation of this feature until the implementation of the keyring dependency is complete. Doing so will allow us to use keyring storage for the appropriate access material.

Documentation on the configuration of an S3 bucket for this use case is extremely desirable and should be targeted at the average user.