{"id":862,"date":"2022-12-12T01:15:00","date_gmt":"2022-12-12T01:15:00","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=862"},"modified":"2022-12-12T01:15:00","modified_gmt":"2022-12-12T01:15:00","slug":"use-aws-cli-create-ec2-instance","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=862","title":{"rendered":"How to Use AWS CLI to Create an EC2 instance [Step by Step]"},"content":{"rendered":"

This blog will teach you to use AWS CLI to create an EC2 instance<\/strong>. Also, we will look at all the possible options available in the CLI.<\/p>\n

Create EC2 instance Using AWS CLI<\/h2>\n

To create an ec2 instance using CLI, you need the following.<\/p>\n

    \n
  1. Security group ID<\/li>\n
  2. Key pair name<\/li>\n
  3. AMI Id<\/li>\n
  4. Subnet ID<\/li>\n<\/ol>\n

    We will create each resource using the CLI. If you have existing resources, you can directly use the respective resource IDs instead of creating them.<\/p>\n

    Get VPC ID and Subnet ID<\/h3>\n

    To create a security group, you need the following two IDs<\/p>\n

      \n
    1. VPC ID:<\/strong> To create a security group<\/li>\n
    2. One<\/strong> Subnet ID: <\/strong>To launch ec2 instance.<\/li>\n<\/ol>\n

      You can get these details from the AWS Management console.<\/p>\n

      Go to the VPC dashboard and click on the VPC. You will get the VPC ID, click on the subnets, and search with the VPC ID to list all the subnets associated with that VPC, as shown below.<\/p>\n

      \"get<\/figure>\n

      I’m going to use the following VPC and subnet IDs for this guide. You need to replace these IDs with your VPC and subnet ID.<\/p>\n

        \n
      1. VPC ID<\/strong>: vpc-0d42bf2f27be967ff<\/code><\/li>\n
      2. Subnet ID<\/strong>: subnet-00b5ede5e160caa59<\/code><\/li>\n<\/ol>\n

        Get AMI Id<\/h3>\n

        Next, you need to get the AMI ID to be used with ec2 CLI.<\/p>\n

        AMI ID could be a base image AMI Id or ID of a custom image created by you or your team.<\/p>\n

        To get the AMI Id, Go to ec2 Dashboard --> AMI Catalog<\/code> and find the list of base images from AWS along with the AMI Id as shown below.<\/p>\n

        \"\"<\/figure>\n

        All the custom AMIs are present under AMIs<\/code> option.<\/p>\n

        I am going to use the AWS Ubuntu AMI id ami-0d70546e43a941d70<\/code>.<\/p>\n

        Create Security Group<\/h3>\n

        Our next requirement is a security group ID to be attached to the ec2 instance. You can attach more than one security group.<\/p>\n

        Either you can use the ID of an existing security group or you can create one using the following command. Replace vpc-0d42bf2f27be967ff<\/code> with your VPC ID<\/p>\n

        aws ec2 create-security-group \\\n    --group-name demo-sg \\\n    --description \"AWS ec2 CLI Demo SG\" \\\n    --tag-specifications 'ResourceType=security-group,Tags=[{Key=Name,Value=demo-sg}]' \\\n    --vpc-id \"vpc-0d42bf2f27be967ff\"<\/code><\/pre>\n
        Note down the security group ID from the output<\/strong>. The output would look like the following.<\/p>\n
        {\n    \"GroupId\": \"sg-07570e17ab8331f13\",\n    \"Tags\": [\n        {\n            \"Key\": \"Name\",\n            \"Value\": \"demo-sg\"\n        }\n    ]\n}<\/code><\/pre>\n
        Refer create-security-group<\/a> official CLI reference for more details.<\/p>\n
        Now, you need to add inbound (ingress) firewall rules to the security group<\/strong>. Replace sg-07570e17ab8331f13<\/code> with your security group ID.<\/p>\n
        aws ec2 authorize-security-group-ingress \\\n    --group-id \"sg-07570e17ab8331f13\" \\\n    --protocol tcp \\\n    --port 22 \\\n    --cidr \"0.0.0.0\/0\" <\/code><\/pre>\n
        If you want to add multiple ports and multiple CIDRs to the security group using the CLI, use the following command.<\/p>\n
        aws ec2 authorize-security-group-ingress \\\n    --group-id \"sg-07570e17ab8331f13\" \\\n    --tag-specifications 'ResourceType=security-group-rule,Tags=[{Key=Name,Value=demo-sg}]' \\\n    --ip-permissions \"IpProtocol=tcp,FromPort=22,ToPort=22,IpRanges=[{CidrIp=0.0.0.0\/0},{CidrIp=10.0.0.0\/24}]\" \\\n    --ip-permissions \"IpProtocol=tcp,FromPort=80,ToPort=80,IpRanges=[{CidrIp=0.0.0.0\/0},{CidrIp=10.0.0.0\/24}]\"<\/code><\/pre>\n
        Create SSH Key Pair<\/h3>\n
        If you have an existing pem key, you can use it. If you don’t, you can create an SSH key pair<\/a> using the following command. The output key gets stored in ~\/.ssh<\/code> location.<\/p>\n
        aws ec2 create-key-pair \\       \n   --key-name  wp-key-03 \\\n   --query 'KeyMaterial' --output text > ~\/.ssh\/demo-key<\/code><\/pre>\n
        Refer ec2 create-key-pair<\/a> CLI reference for more details.<\/p>\n
        AWS CLI Command to Create ec2<\/h3>\n
        Now we have the following pre-defined values.<\/p>\n
          \n
        1. VPC ID<\/strong>: vpc-0d42bf2f27be967ff<\/code><\/li>\n
        2. Subnet ID<\/strong>: subnet-00b5ede5e160caa59<\/code><\/li>\n
        3. AMI ID<\/strong>: ami-0d70546e43a941d70<\/code><\/li>\n
        4. Security Group ID:<\/strong> sg-063c02687e1103c7b<\/li>\n
        5. Key name:<\/strong> demo-key<\/li>\n<\/ol>\n
          Here is an example AWS CLI command to create an ec2 instance.<\/p>\n
          aws ec2 run-instances \\\n    --image-id ami-0d70546e43a941d70 \\\n    --count 1 \\\n    --instance-type t2.micro \\\n    --key-name bibin-server \\\n    --security-group-ids sg-07570e17ab8331f13 \\\n    --subnet-id subnet-00b5ede5e160caa59 \\\n    --block-device-mappings \"[{\\\"DeviceName\\\":\\\"\/dev\/sdf\\\",\\\"Ebs\\\":{\\\"VolumeSize\\\":30,\\\"DeleteOnTermination\\\":false}}]\" \\\n    --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=demo-server}]' 'ResourceType=volume,Tags=[{Key=Name,Value=demo-server-disk}]'<\/code><\/pre>\n
          Following are some of the important parameters you should know.<\/p>\n
          <\/p>\n\n\n\n\n\n\n\n\n\n
          Parameter<\/th>\nDetails<\/th>\n<\/tr>\n<\/thead>\n
          --block-device-mappings<\/code><\/td>\nTo set the custom volume size for the root volume \/dev\/sdf<\/code>. You can also add additional volumes using this parameter.<\/td>\n<\/tr>\n
          --monitoring<\/code><\/td>\nTo enable detailed ec2 monitoring<\/td>\n<\/tr>\n
          --ebs-optimized<\/code><\/td>\nTo optimize ec2 for EBS IO<\/td>\n<\/tr>\n
          --iam-instance-profile<\/code><\/td>\nTo add instance profile (IAM role) to the instance.<\/td>\n<\/tr>\n
          --launch-template<\/code><\/td>\nTo launch the ec2 instance from a launch template. <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
          <\/p>\n
          Refer ec2 run-instances<\/a> official CLI documentation for all the parameter references.<\/p>\n
          AWS CLI Command to Create ec2 Instance With User Data<\/h3>\n
          With ec2 CLI, you can pass the <\/strong>ec2 user data<\/strong><\/a> script<\/strong> using the --user-data<\/code><\/strong> flag.<\/p>\n
          First, create a user data script file. For example,  a shell script named script.sh<\/code><\/strong><\/p>\n
          #!\/bin\/bash\napt-get update -y\nsudo systemctl nginx start\nchkconfig nginx on<\/code><\/pre>\n
          Now, along with the ec2 create CLI command we have learned in the last section, just add the --user-data<\/code> flag with the file path as highlighted below. You can provide the relative path or the absolute path of the script file based on your requirements.<\/p>\n
          aws ec2 run-instances \\\n    --image-id ami-0d70546e43a941d70 \\\n    --count 1 \\\n    --instance-type t2.micro \\\n    --key-name bibin-server \\\n    --security-group-ids sg-07570e17ab8331f13 \\\n    --subnet-id subnet-00b5ede5e160caa59 \\\n    --block-device-mappings \"[{\\\"DeviceName\\\":\\\"\/dev\/sdf\\\",\\\"Ebs\\\":{\\\"VolumeSize\\\":30,\\\"DeleteOnTermination\\\":false}}]\" \\\n    --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=demo-server}]' 'ResourceType=volume,Tags=[{Key=Name,Value=demo-server-disk}]' \\\n    --user-data file:\/\/path\/to\/script.sh<\/code><\/pre>\n
          If it is a single-line command, you can pass it directly without an external file as shown below.<\/p>\n
          --user-data sudo systemctl nginx start<\/code><\/pre>\n
          Conclusion<\/h2>\n
          In this step-by-step guide, we learned to use AWS CLI to create an ec2 instance.<\/p>\n
          If you are a DevOps engineer working on the AWS cloud, learning to use AWS CLI to create AWS resources is essential. You can use it for automation as well as ad-hoc tasks.<\/p>\n
          Also, if you are learning AWS, check out my comprehensive guide to becoming a DevOps engineer<\/a>, where I talk about what to learn on the AWS cloud.<\/p>\n
          \n
          Ngu\u1ed3n:<\/strong> How to Use  AWS CLI to Create an EC2 instance [Step by Step] \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
          Source: https:\/\/devopscube.com\/use-aws-cli-create-ec2-instance\/<\/p>\n","protected":false},"author":1,"featured_media":863,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-862","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/862","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=862"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/862\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/863"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=862"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=862"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=862"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}