-
Notifications
You must be signed in to change notification settings - Fork 13
AWS Account Creation and Setup
Jeremy Anderson edited this page Feb 11, 2015
·
2 revisions
##Signing up for your AWS account
Important: You will need a credit card if you choose to create an AWS account. It is your responsibility to close the account after use to avoid any additional charges.
Note: Part of the sign-up procedure involves receiving a phone call and entering a PIN using the phone keypad.
- Go to http://aws.amazon.com, and then click Sign Up.
- Follow the on-screen instructions.
- Additional information on getting started with AWS can be found at http://aws.amazon.com/getting-started/
- Open the Amazon EC2 console.
- From the navigation bar, select US East (N. Virginia) Region for the key pair.
- Click Key Pairs in the navigation pane.
- Enter a name for the new key pair in the Key pair name field of the Create Key Pair dialog box, click Create.
- The private key file is automatically downloaded by your browser. The base file name is the name you specified as the name of your key pair, and the file name extension is .pem. Save the private key file in a safe place. (ie. ~/.ssh/my-key-pair.pem)
Mac and Linux
- If you are on a Mac or Linux system and do not have a .ssh directory, run the command below from a terminal.
mkdir ~/.ssh/
- Move your private key to the .ssh directory.
mv ~/Downloads/<my-key-pair.pem> ~/.ssh
- Set the correct permissions.
chmod 400 ~/.ssh/<my-key-pair.pem>
Windows
- If you are on a Windows system, please follow the instructions on converting your .pem key to a .ppk using PuTTygen
- From the AWS console navigate to Services --> EC2 and click on Launch Instance
- You should now be in the Choose AMI menu. Click on Community AMIs and search for ami-45f6d375 click Select
- Select a size for the instance. Click Configure Instance Details (It is recommend that you use an m3.large, you may select a smaller size but it may take longer to run the pipeline. Some tools, such as bwa.kit, behave poorly when given insufficient RAM. Our testing indicates that an m3.large should provide enough memory to let all the command line otols work. Also note that anything smaller than an m3.medium will have to be launched into a VPC, which is a bit more of an advanced topic.)
- Make sure that Network is set to EC2 Classic. Click Add Storage
- Under Size (GiB) ensure 150GB are allocated to the Root drive. Click Tag Instance
- You may enter a name for your new instance in the Value field. Click Configure Security Group
- You can leave the default configurations. Click Review Instance Launch
- Ensure all settings are correct and click Launch
- You will be prompted to select a Key Pair. Select Choose an existing key pair and select the key pair you generated earlier from the drop down list. Check the acknowledgement box and click Launch Instance
- It should take about a minute to launch the new instance. You can check the status of the instance by going to Services --> EC2 --> Instances
- When the instance finishes launching you may ssh to it from a terminal window on Mac or Linux by running the command below:
ssh -i <path-to-private-key> ubuntu@<your-public-ip-address>
If you are using a Windows system, please follow the instructions found here
- Home
- DaSH 15 (Utrecht) 2024
- DaSH 14 (Oklahoma City) 2024
- DaSH 13 (Rochester) 2023
- DASH VRS (Virtual) 2022
- DASSH3 (Virtual) 2020
- DASH12 (Virtual) 2022
- DASSH4 (Virtual) 2021
- DASH11 (Virtual) 2021
- DASSH3 (Virtual) 2020
- DASH10 (Virtual) 2020
- DASH Validation (Minneapolis) 2020
- DaSSH 2 (Minneapolis) 2019
- DASH9 (Denver) 2019
- DASH8 (Baltimore) 2018
- DASSH FHIR (Minneapolis) 2018
- DASH7 (Utrecht) 2017
- DASH IHIWS (Stanford) 2017
- DASH6 (Heidelberg) 2017
- DASH5 (Berkeley) 2017
- DASH4 (Vienna) 2016
- DASH3 (Minneapolis) 2016
- DASH2 (La Jolla) 2015
- DASH1 (Bethesda) 2014
- Preparing for the Hackathon
- Tool access
- Tools
- Data
- Github help