-
Notifications
You must be signed in to change notification settings - Fork 1
Getting Started
The content of this tutorial assumes you are familiar with the following:
- Using SSH to access remote servers, including creating/adding keys
- ...
You must have access to an AWS account to follow this tutorial. Access should be via an IAM user login; using the root account credentials is not recommended. If you are working in a temporary or sandbox account, the "AdministratorAccess" IAM role will allow you to perform all of the required changes; this role will need to be applied to your user account, or can be attached to an EC2 instance. If you wish to use the AWS CLI with authentication as an IAM user, you will need to provide your API keys when configuring the CLI. If instead to use a role attached to an EC2 instance, you will automatically have the required permissions once logged in to that instance, without the need for API keys.
If you are working within an organisationally-managed AWS account and do not have permissions to modify IAM users/roles, contact your account admin. They will be able to assist by either provisioning a role to your user account with appropriate (though likely more limited) permissions, or providing access to an EC2 instance which has the required role. Provisioning a static HPC cluster requires the ability to create EC2 instances and networking components, while deploying a dynamically scaling cluster additionally requires the creation of custom IAM policies and roles, which in turn allow instances to be created and terminated automatically.
[Add warning about loose permissions -> risk of unexpected charges if not careful]
[Mention quotas - no need to increase for the purposes of this tutorial]
[Simple description of creating an EC2 instance in the console]
[Note on adding IAM roles to allow API-key-free CLI usage]
[Note on default usernames - centos vs ec2-user]
[Description of what C9 is, what its advantages are for this use-case]
[Description of creating a C9 instance in the console]