AWS - Release History, Roadmap

Version 2.0 (2021): Security and organization update

Implemented AWS control tower in our new AWS orgs so all newly provisioned AWS accounts will be in those managed orgs.
New orgs have new security policies in place to provide some security guardrails.
One of the new AWS organizations is for NIH STRIDES accounts, giving biomedical researchers especially those with NIH funding much better rates and Enterprise support.
We have BAA (Business Associate Agreement(s)) in place for our AWS accounts, as required for HIPAA.
Customers can manage sensitive or restricted data in AWS, with the completion of a Risk Assessment by Cybersecurity.

Version 1.1 (03.01.2019): Pricing update:

The net cost to campus customers will be equal to Amazon's published rates for AWS, but will include a 15% network egress waiver (15% based on total UW AWS monthly spend)

Version 1.0 (08.01.2016): Technical pilot. Features:

The entire suite of generally available AWS compute services including Amazon Simple Storage Service (S3) and Amazon Elastic Compute Cloud (EC2)
The ability for customers to process, store, or otherwise propagate internal and public data in AWS
The ability for users to sign in to the AWS Management Console using their NetID
The net cost to campus customers will be 2% more than Amazon's published rates for AWS, but will include a 15% network egress waiver

The surcharge has been approved by the CIO, but is currently only an estimated rate. Data will be collected on this charge this fiscal year and may be adjusted up or down in the future based on actual costs

Version 1.0 of the campus AWS offering does not include:

The ability for customers to provision resources in campus IP space
The ability for customers to process, store, or otherwise propagate sensitive or restricted data in AWS
AWS Mechanical Turk is not included in the DLT/Internet2 contract
AWS offerings in Beta may not be available to DLT/Internet2 customers

See Also