...
What is the AWS Data Egress Waiver?
AWS offers a Data Egress Waiver that mostly eliminates Data Transfer charges for Cornell. See the AWS blog post about it for more details.
...
How much are Data Transfer Charges for Cornell? Are we close to the 15% cap for the AWS Data Egress Waiver?
This chart of recent billing data shows that In short, no, Cornell is not near the 15% cap of the Data Egress Waiver.
...
As of March 2023, the last three months averaged 6.83% utilization and the last six averaged 6.16%. If more detailed information is needed, please contact cloud-support@cornell.edu.
Billing
I got an invoice for AWS from CloudCheckr. What should I do with it?
...
As of June 2022, individual Cornell AWS accounts cannot buy Reserved Instances or Savings Plans. Cornell has a program that purchases those centrally. See
Licensing
For more information, please contact the Cloud Team.
Licensing
Does the Does the Cornell Microsoft Agreement cover Microsoft software in AWS?
...
Can I use Mechanical Turk with my Cornell AWS account?
- Mechanical Turk requestor requester accounts can use the same email address and password as AWS root accounts.
However, in order to keep these concerns separate, we recommend using different email accounts for each of AWS, Amazon.com retail store, and Mechanical Turk. - As of December 2020, MTurk accounts can be linked to AWS accounts for billing purposes.
MTurk accounts linked like that have their charges included in the charges for the AWS account. Please contact cloud-support@cornell.edu to link your MTurk account.- With this linkage, research awards/credits issued by AWS to an AWS account can be used for paying MTurk charges.
- Only one MTurk account can be linked to each AWS account.
- In order to establish this linkage, the root credentials for the AWS account must be used.
If the Cloud Team manages the root credentials for an AWS account, we will be happy to help establish this linkage. Please contact cloud-support@cornell.edu.
- As of August 2023 , New MTurk Requester accounts that are created and linked to AWS accounts , the Requester UI is ONLY available using the ROOT login for the account , not another email account.
- One can specify on the MTurk Account page a Requster name and alternate email for Contact by workers , and a Display Name .
- One can still use an SDK / CLI script management of the Requester using User Access Keys in the AWS Account that have Mechankical Turk permissions thru attached policies.
- Alternatively one can use a 3rd party solution like CloudResearch that can provide a UI and use AccessKeys to manage the MTurk Requester functions; Creting HITs, setup Sandbox, and interact with Workers, vet workers etc.
Can I use tagging in Mechanical Turk?
...