On github.com, you can view the table of contents (outline) of this file by clicking the menu icon (three lines or dots) in the top corner. It's next to the pencil "edit" icon and below the word "History".
To download files from Amazon S3, first install via
sudo easy_install awscli
aws configureand then run a command such as
aws s3 sync s3://bucketname .For example:
mkdir -p ~/tmp/aws-s3
cd ~/tmp/aws-s3
aws s3 sync s3://travis-checker-framework .Doing aws s3 sync s3://travis-checker-framework/typetools/checker-framework/1048/1048.1 .
copies the contents of that remote directory to the current local directory.
To delete/remove files:
aws s3 rm --recursive s3://travis-checker-framework/typetoolsAmazon Web Services (AWS) tips, from Darioush Jalali:
- Billing is not logged by default. This can be confusing if you are trying to figure out how much money you are spending initially.
- If you have jobs that can be restarted easily, spot instances are up to 10x cheaper than on-demand instances. Amazon may turn them off whenever they choose (this is rare).
- Amazon limits the number of types of certain instances they grant. Customer support will increase this, but it takes a couple days.
Cloud credits for research from AWS and EC2, for experiments: https://aws.amazon.com/research-credits/
There is no requirement on the account you use for GCP (i.e., it can be your
personal account,
does not need to be a @uw.edu account).
The first step is to create a GCP organization, under which you'll create a project.
An organization is the top-level entity in GCP under which all projects are organized.
A project houses resources you can spin up in GCP,
such as VMs,
storage,
and access to LLMs APIs.
Follow these instructions
to create an organization.
Once you have created an organization, you can create a project. A project is the "base level where all Google Cloud services (APIs) are enabled and where resource like Compute Engine instances or BigQuery datasets are created.". Ensure you are on the project you created on the GCP Console. After you've created the project, ensure that you've set up billing for it, otherwise you will not be able to use any resources. Set up billing by going to the "Billing" menu from the hamburger menu that appears in the top left-hand corner.
You'll then need to enable the API you want to use in the project: (select the project from the project picker on the top bar).
- Select the "API & Services" menu from the hamburger menu that appears in the top left-hand corner.
- Select "Enable APIs and services" and choose the API you want to enable (e.g., Vertex AI API).
After this is complete, try to generate an API key for your project. If this setting is disabled, you are likely missing permissions at the organization level that you'll need to set (recall that your project lives underneath your org, and inherits all permissions from it). You'll likely need to grant yourself (in your organization) the "Organization Policy Administrator" and the "Organization Administrator" roles:
- Go to GCP and select the organization under which your project has been created.
- Click on IAM & Admin from the hamburger menu.
- Edit your user and add Roles: "Organization Policy Administrator" and "Organization Administrator".
- If theses roles don't appear, double-check that you have selected your organization and not your project.
- Now with those 2 roles, click on "Organization Policies" under IAM & Admin, then select "Organization Policies".
- Search for "Disable service account key creation" and edit as required.
Try creating the API key again.