Set up to use Amazon EC2 - Amazon Elastic Compute Cloud
Sign up for an Amazon Web Services accountSecure IAM usersCreate a key pairCreate a security group
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Set up to use Amazon EC2

Complete the tasks in this section to get set up for launching an Amazon EC2 instance for the first time:

  1. Sign up for an Amazon Web Services account

  2. Secure IAM users

  3. Create a key pair

  4. Create a security group

When you are finished, you will be ready for the Amazon EC2 Getting started tutorial.

Sign up for an Amazon Web Services account

If you do not have an Amazon Web Services account, use the following procedure to create one.

To sign up for Amazon Web Services

  1. Open http://www.amazonaws.cn/ and choose Sign Up.

  2. Follow the on-screen instructions.

Amazon sends you a confirmation email after the sign-up process is complete. At any time, you can view your current account activity and manage your account by going to http://www.amazonaws.cn/ and choosing My Account.

Secure IAM users

After you sign up for an Amazon Web Services account, safeguard your administrative user by turning on multi-factor authentication (MFA). For instructions, see Enable a virtual MFA device for an IAM user (console) in the IAM User Guide.

To give other users access to your Amazon Web Services account resources, create IAM users. To secure your IAM users, turn on MFA and only give the IAM users the permissions needed to perform their tasks.

For more information about creating and securing IAM users, see the following topics in the IAM User Guide:

Create a key pair

Amazon uses public-key cryptography to secure the login information for your instance. A Linux instance has no password; you use a key pair to log in to your instance securely. You specify the name of the key pair when you launch your instance, then provide the private key when you log in using SSH.

If you haven't created a key pair already, you can create one by using the Amazon EC2 console. Note that if you plan to launch instances in multiple Amazon Web Services Regions, you'll need to create a key pair in each Region. For more information about Regions, see Regions and Zones.

To create your key pair

  1. Open the Amazon EC2 console at https://console.amazonaws.cn/ec2/.

  2. In the navigation pane, choose Key Pairs.

  3. Choose Create key pair.

  4. For Name, enter a descriptive name for the key pair. Amazon EC2 associates the public key with the name that you specify as the key name. A key name can include up to 255 ASCII characters. It can’t include leading or trailing spaces.

  5. For Key pair type, choose either RSA or ED25519. Note that ED25519 keys are not supported for Windows instances.

  6. For Private key file format, choose the format in which to save the private key. To save the private key in a format that can be used with OpenSSH, choose pem. To save the private key in a format that can be used with PuTTY, choose ppk.

  7. Choose Create key pair.

  8. 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 determined by the file format you chose. Save the private key file in a safe place.

    Important

    This is the only chance for you to save the private key file.

  9. If you plan to use an SSH client on a macOS or Linux computer to connect to your Linux instance, use the following command to set the permissions of your private key file so that only you can read it.

    chmod 400 key-pair-name.pem

    If you do not set these permissions, then you cannot connect to your instance using this key pair. For more information, see Error: Unprotected private key file.

For more information, see Amazon EC2 key pairs and Linux instances.

Create a security group

Security groups act as a firewall for associated instances, controlling both inbound and outbound traffic at the instance level. You must add rules to a security group that enable you to connect to your instance from your IP address using SSH. You can also add rules that allow inbound and outbound HTTP and HTTPS access from anywhere.

Note that if you plan to launch instances in multiple Amazon Web Services Regions, you'll need to create a security group in each Region. For more information about Regions, see Regions and Zones.

Prerequisites

You'll need the public IPv4 address of your local computer. The security group editor in the Amazon EC2 console can automatically detect the public IPv4 address for you. Alternatively, you can use the search phrase "what is my IP address" in an internet browser, or use the following service: Check IP. If you are connecting through an Internet service provider (ISP) or from behind a firewall without a static IP address, you need to find out the range of IP addresses used by client computers.

You can create a custom security group using one of the following methods.

New console
To create a security group with least privilege

  1. Open the Amazon EC2 console at https://console.amazonaws.cn/ec2/.

  2. From the top navigation bar, select an Amazon Web Services Region for the security group. Security groups are specific to a Region, so you should select the same Region in which you created your key pair.

  3. In the left navigation pane, choose Security Groups.

  4. Choose Create security group.

  5. For Basic details, do the following:

    1. Enter a name for the new security group and a description. Use a name that is easy for you to remember, such as your user name, followed by _SG_, plus the Region name. For example, me_SG_uswest2.

    2. In the VPC list, select your default VPC for the Region.

  6. For Inbound rules, create rules that allow specific traffic to reach your instance. For example, use the following rules for a web server that accepts HTTP and HTTPS traffic. For more examples, see Security group rules for different use cases.

    1. Choose Add rule. For Type, choose HTTP. For Source, choose Anywhere.

    2. Choose Add rule. For Type, choose HTTPS. For Source, choose Anywhere.

    3. Choose Add rule. For Type, choose SSH. For Source, do one of the following:

      • Choose My IP to automatically add the public IPv4 address of your local computer.

      • Choose Custom and specify the public IPv4 address of your computer or network in CIDR notation. To specify an individual IP address in CIDR notation, add the routing suffix /32, for example, 203.0.113.25/32. If your company or your router allocates addresses from a range, specify the entire range, such as 203.0.113.0/24.

      Warning

      For security reasons, do not choose Anywhere for Source with a rule for SSH. This would allow access to your instance from all IP addresses on the internet. This is acceptable for a short time in a test environment, but it is unsafe for production environments.

  7. For Outbound rules, keep the default rule, which allows all outbound traffic.

  8. Choose Create security group.

Old console
To create a security group with least privilege

  1. Open the Amazon EC2 console at https://console.amazonaws.cn/ec2/.

  2. In the left navigation pane, choose Security Groups.

  3. Choose Create Security Group.

  4. Enter a name for the new security group and a description. Use a name that is easy for you to remember, such as your user name, followed by _SG_, plus the Region name. For example, me_SG_uswest2.

  5. In the VPC list, select your default VPC for the Region.

  6. On the Inbound rules tab, create the following rules (choose Add rule for each new rule):

    • Choose HTTP from the Type list, and make sure that Source is set to Anywhere (0.0.0.0/0).

    • Choose HTTPS from the Type list, and make sure that Source is set to Anywhere (0.0.0.0/0).

    • Choose SSH from the Type list. In the Source box, choose My IP to automatically populate the field with the public IPv4 address of your local computer. Alternatively, choose Custom and specify the public IPv4 address of your computer or network in CIDR notation. To specify an individual IP address in CIDR notation, add the routing suffix /32, for example, 203.0.113.25/32. If your company allocates addresses from a range, specify the entire range, such as 203.0.113.0/24.

      Warning

      For security reasons, do not allow SSH access from all IP addresses to your instance. This is acceptable for a short time in a test environment, but it is unsafe for production environments.

  7. On the Outbound rules tab, keep the default rule, which allows all outbound traffic.

  8. Choose Create security group.

Command line
To create a security group with least privilege

Use one of the following commands:

For more information, see Amazon EC2 security groups for Linux instances.