- Created by user-07789, last modified by Scott M. Sorrentino on May 20, 2019
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 31 Next »
Mission: Facilitate Cornell's transition to the cloud while encouraging modern DevOps practices.
Cornell Cloud Questions?
- Search this wiki for answers. Use the side bar search → → →
- Send your question to cloud-support@cornell.edu
- Connect with cloud practitioners. See Connecting with the CIT Cloud Team and Cornell's Cloud Community
- Request support from AWS. See AWS Support and Escalation
Featured Info
-
Page:Free or Open Source Resources to Help with AWS Security — An annotated list of free resources and open source tools to assist with AWS security
-
Page:Azure FAQs — Answers to questions about Azure that we often see at Cornell
-
Page:Benefits of AWS Accounts under the Cornell-AWS Umbrella — We encourage all Cornell teams, staff, and faculty to contact the Cloud Team (cloud-support@cornell.edu) if they have an AWS account that they use for Cornell business or research purposes and that is not part of the contract that Cornell has with AWS. Here are some of the benefits of getting a new AWS account, or bringing an existing AWS account to the master Cornell-AWS contract.
-
Page:Cornell Active Directory Groups for use with AWS Shibboleth (Cornell Two-Step Login) — The integration between Cornell CUWebAuth (and Cornell Two-Step Login) and AWS requires Active Directory groups with specific characteristics. When the Cloud Team asks a Cornell AWS account owner to request an Active Directory group from their unit IT support for gating access to roles in the AWS console the following wording can be used in the request.
-
Page:AWS FAQs — Answers to questions about AWS that we often see at Cornell.
-
Page:Access Keys for AWS CLI Using Cornell Two-Step Login - Shibboleth — This document shows how to setup and use the awscli-login tool to retrieve temporary AWS access keys using your Cornell netid credentials and Duo (i.e., Cornell Two-Step Login). Using temporary access keys associated with an AWS role to authenticate to the AWS Command Line Interface (CLI) is much safer than using fixed AWS access keys tied to an IAM user. Now that this option is available to Cornell AWS users, we recommend that fixed access keys no longer be used for humans using the AWS CLI.
-
Page:Cornell AWS Direct Connect Routing Diagrams — This page shows and discusses the different routing options over the Cornell Direct Connect to AWS VPCs.
-
Page:
-
Page:Common Azure and AWS Terminology — Folks familiar with AWS who are learning Azure or who are familiar with Azure and learning AWS commonly find it challenging to map terminology from one service to the other. This page provides a mapping between services and names of resource types from each vendor. We include only the most commonly used services and terms.
-
Page:Connecting with the CIT Cloud Team and Cornell's Cloud Community — There are many ways to connect with the Cloudification Team and others at Cornell working on cloud technologies.
-
Page:
Public Topics
- About Cloud Infrastructure & Solutions Engineering Services
- AWS
- Azure
- Cloud Services Training
- Cloud Tools Training
- Common Azure and AWS Terminology
- Connecting with the CIT Cloud Team and Cornell's Cloud Community
- General "How To" Documents
- Public Projects
- Standard Tagging
- VDI, Application Streaming and Application Virtualization
Search within Cloudification Space
Recently Updated
- No labels