dopahero.blogg.se - Ec2 install tcpdump

The following is the output of the above command. So, we have to pipe the output to base64 and decode the value as show here.

base64 –decode – The output is in base64.

–query “UserData.Value” – We are specifically querying for the UserData.Value.

–output text – We want to output in text format.

–instance-id – Specify the instance id for which we want to view the attribute.

–attribute userData – This indicates that the attribute we are interested is userData.

aws ec2 describe-instance-attribute – This is the command to view any attribute of the specified instance.

attribute userData -output text -query "UserData.Value" \ Use the aws ec2 describe-instance-attribute -instance-id i-08dae85dc8fa85aa2 \ To view the Userdata that was used while creating your instance, do the following:įor this, use the describe-instance-attribute option in the “aws ec2” command as shown below. View the UserData of an Existing EC2 Instance from CLI

Specify the above ud.txt file during the instance creation in the run-instances command as shown below: aws ec2 run-instances -image-id ami-a4c7edb2 -count 1 \ This is helpful when you want your newly created instance to be in a certain state with certain packages installed, or with certain custom configuration.Ĭreate your custom userdata file. You can use Userdata file during an instance creation to execute your custom commands. Create a new EC2 Instance with UserData from CLI There are many things you can do using the aws ec2 CLI utility as we discussed earlier: 15 Essential Amazon AWS EC2 CLI Command Examples 2. If you specify an invalid AMI image id, you’ll get the following InvalidAMIID.Malformed error: A client error (InvalidAMIID.Malformed) occurred when calling the RunInstances operation: Invalid id: "ami-a4c7edbm"

# aws ec2 run-instances -image-id ami-a4c7edb2 -count 1 -instance-type t2.micro -key-name mynewkey -security-groups my-aws-security-group -subnet-id subnet-8534a4afĪ client error (InvalidParameterCombination) occurred when calling the RunInstances operation: The parameter groupName cannot be used with the parameter subnet If you specify a parameter that cannot be used in the combination you are using, you’ll get the following InvalidParameterCombination error message.

A subnet ID or network interface ID is required to carry out the request. If you don’t specify the network interface, you’ll get the following VPCResourceNotSpecified error message: A client error (VPCResourceNotSpecified) occurred when calling the RunInstances operation: The specified instance type can only be used in a VPC.

–subnet-id subnet-5630306b – This is the network VPC where I want to create the new EC2 server.

–key-name mynewkey – Use the key pair that you’ve already created and have it on your AWS account.

–instance-type t2.micro – Specify the instance type here.

Be very careful with this parameter, you don’t want to by mistake specify a higher number here, as it will create those many number of servers, which will be charged to your account.

–count 1 This indicates that we want to create just one new server with this image.

–image-id ami-a4c7edb2 – This is the image id of the image that we will be using to create a new instance.

aws ec2 run-instances – This is the command to launch new Amazon EC2 instance.

instance-type t2.micro -key-name mynewkey \ To launch a new server from an image, use the run-instances option along with “aws ec2” command as shown below: # aws ec2 run-instances -image-id ami-a4c7edb2 -count 1 \ The repositories include Docker, PHP, MySQL, PostgreSQL, and other packages. The default image includes AWS command line tools, Python, Ruby, Perl, and Java. This is the description of this particular image: The Amazon Linux AMI is an EBS-backed, AWS-supported image. In this example, the image we are using is called “Amazon Linux AMI 2017.03.1 (HVM), SSD Volume Type” with this image id: ami-a4c7edb2.