Amazon Web Services (AWS)
Departments and units at the University of Georgia may purchase Amazon Web Services (AWS) through the standard procurement process in UGAMart. Units must first complete a CESS approval form to participate and follow the program guidelines.
Note: AWS third-party professional services are not available under this program.
Faculty, Staff and IT Professionals
- The scope of initial services available under this program includes the entire suite of Amazon Web Services (AWS). AWS third-party professional services are not available under this program.
- All projects requiring AWS cloud services will require a CESS approval. Make sure to review the CESS guidelines.
- All Data Management/Classification Standards must be adhered to.
- A Financial Stewardship Form must be completed and signed by the Dean or Vice President prior to initiating a purchase requisition or setting up each master account with AWS. A copy of the signed form must be attached to each AWS purchase requisition in UGAMart.
- Initial purchase requisitions and purchase order amendments must total less than $25,000 per fiscal year.
- Any regulatory contract requirements for HIPAA (BAA), PHI, FERPA, etc. must be in compliance at all times.
- Only purchase orders will be allowed for procurement of cloud services.
- Each university unit/department is responsible for monitoring usage/costs of and setting
fiscal cap alerts for all approved cloud service accounts to avoid budget overages.
- The designated departmental technical representative will be the primary point of contact for a department’s AWS master account and sub-account administration.
- The department’s chief fiscal officer has oversight responsibility for cost management and internal control compliance.
- An account will be subject to cancellation by the vendor or UGA if cumulative spending exceeds the PO amount or vendor usage allowances.
- UGA’s Chief Technology Officer and Chief Information Security Officer will have oversight of and system access to all UGA AWS accounts to monitor use and security of restricted data. Any required remediation actions will be taken only after notifying the respective departmental technical contact and Dean or Vice President.
- The departmental technical contact will be responsible for all other system administration: data backups, database management, passwords, disaster recovery, and data security measures.
- Once a project proposal has been developed/approved, submit a CESS request inUGAmart.
- Estimate total cost of ownership (TCO) using the AWS TCO Calculator and your monthly usage/cost using the AWS Monthly Cost Calculator. Both calculators can be found here.
- You must designate if the requested services will be used to handle sensitive/restricted data subject to regulatory requirements, such as HIPAA (and as such, will be covered under the Business Associate Addendum (BAA) agreement between the University and AWS). Quoted pricing for BAA eligible services will be somewhat higher than standard AWS service pricing (averages 1-10% higher).
- Support options will be quoted along with the services.
- Your AWS Services request is governed by the Enterprise Agreement between the University System of Georgia and Amazon Web Services; such agreement determines terms, conditions and pricing.
- Complete and attach the following support documents to theUGAMart cart:
- AWS quote
- Financial Stewardship Form
- Add an internal note/comment in the cart if the BAA will apply and that the quote reflects BAA adjusted pricing.
- For any new purchases against an existing master account or a sub-account under this master account, a copy of the original signed financial stewardship form should be attached to the PR with the original PO referenced. Also, note the applicable master/sub-account number in the internal notes section of the PR.
AWS will invoice actual usage to each master account holder on a monthly basis.
Once the PO has been issued to AWS, the departmental technical contact should follow AWS’ online instructions for account creation, setting up fiscal cap alerts and management reporting and linking the department’s master account to UGA’s account list.
- Account set up instructions
- AWS Management Console alert and reporting set up can be done here.
- Set up master/sub account structure, financial cap alerts and internal process controls with the departmental business office and fiscal officer.
- After the master account is created, please email your contact information, including UGA’s legal name of “The Board of Regents of the University System of Georgia on and behalf of the University of Georgia," and AWS account number to email@example.com , so the account can be added to UGA’s accounts list.
Each departmental technical representative is responsible for all system administration, including access, removal, and transfer of responsibility for all unit/department end users supported.
Contact the UGA-dedicated AWS Account team if you need assistance with:
- Demos, presentations, meetings, proofs of concepts to help explain AWS Services as it relates to the university project
- Architectural Designs. AWS will architect for you or with you, and can review your architectural plans
- Pricing AWS Services
- Researchers’ Cost Models. AWS will develop a cost model for inclusion in researchers’ grants prior to submission
- Letters of Support. AWS will provide Letter of Support for inclusion in researchers’ grants prior to submission.
- Research Grants from AWS
AWS Contact Information
1. Reserved Instances:
- For AWS Services that qualify for Reserved Instances, please go here; (services are Amazon Elastic Compute Cloud (Amazon EC2), Amazon Relational Database Service (Amazon RDS), Amazon Redshift and Amazon ElastiCache) and here.
- Reserved Instance types can be found here.
2. Find information on Workspaces, including Microsoft licensing information, here.
3. Find support options here.