Skip to end of banner
Go to start of banner

AWS Info

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Developer AWS Accounts

Use your individual AWS account under the Sage consolidated bill for AWS experiments. The rule of thumb is that if you cannot shut off what ever you are running while you are on vacation, it belongs in the Production AWS Account.

Production AWS Account

The user name is platform@sagebase.org. Ask a teammate for the password.

Right now IAM does not facilitate access to the AWS Console so we will share this user name and password for now. Later on we will all be in the IAM administrators group.

How To

Upload a dataset to S3

For the initial upload, a GUI tool called BucketExplorer (http://www.bucketexplorer.com/) is used. Uploads are done from the internal host fremont.fhcrc.org using the local access account 'platform', with the same password as the platform@sagebase.org account. The most efficient way to connect is to use an NX protocol client (http://www.nomachine.com/download.php) to get a virtual desktop as the user platform. Once connected the preconfigured BucketExplorer can be found in the application menu in the lower left corner of the screen.

The initial datasets are stored in /work/platform/. This entire collection is mirrored exactly and can transfered by dragging and dropping into the data01.sagebase.org s3 bucket. BucketExplorer is very efficient, and will do hash comparisons and only transfer what files have changed. One can also get a visual comparison of what files have changed using the 'Comparer' button. During the transfer, BucketExplorer will parallelize the transfer into 20 streams for very efficient use of outgoing bandwidth to the cloud. 

Create a new IAM group

TODO deflaux: talk about Sage-specific stuff such as where we want to check in our policy files to SVN for each group

Create a new user and add them to IAM groups

TODO deflaux: for Sage employees getting read/write access talk about where to store their credentials because we can only see them at user creation time

Per Brian, he recommends that we store them in our server home directory on beltown/fremont so that they are backed up

  • No labels