aws-command-line-clir

# https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html
# https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html
# Identifying the EBS Device

# Other Linux
nvme id-ctrl -v /dev/nvme8n1p1 | head -n5
NVME Identify Controller:

# AmazonLinux

[ec2-user ~]$ sudo /sbin/ebsnvme-id /dev/nvme1n1
Volume ID: vol-01324f611e2463981
/dev/sdf


# KMS KEY & ALIAS CREATION
#######################################################################################
#!/bin/bash

# https://docs.aws.amazon.com/cli/latest/reference/kms/create-alias.html

echo -e "\nBest is to create the KMS Key Manually, because I foud the fields do change & behave differently because of A/c "string" length, so this is a demo, that is why I am using it.\n"


ACCOUNT_ID=`aws sts get-caller-identity | grep -i "account" | cut -d':' -d'"' -f4`
#KMS_KEY=`aws kms create-key | grep "key" | awk '{print $3}' | cut -f6 -d":" | cut -d"/" -f2`
ALIAS_NAME="jenkins"

KMS_KEY=`aws kms create-key | grep "key" `

echo -e "\nYour AWS A/c ID is "$ACCOUNT_ID"\n"

echo "$KMS_KEY"
echo -e 'aws kms create-alias --alias-name alias/YourAlias --target-key-id CopyTheTargetKMSkeyFromAbove&PasteHere'
echo 'aws kms list-aliases | grep "YourAlias"'



#END



##############################################################################################
# List All Stopped instances

# https://stackoverflow.com/questions/46457899/aws-cli-command-to-list-stopped-instances

aws ec2 describe-instances --filters  "Name=instance-state-name,Values=stopped" --query 'Reservations[].Instances[].Tags[?Key==`Name`].Value[]'

aws ec2 describe-instances --filters  "Name=instance-state-name,Values=stopped" --query 'Reservations[].Instances[].{ID: InstanceId,Hostname: PublicDnsName,Name: Tags[?Key==`Name`].Value }'

# List All Running Instances

aws ec2 describe-instances --filters  "Name=instance-state-name,Values=running" --query 'Reservations[].Instances[].{ID: InstanceId,Hostname: PublicDnsName,Name: Tags[?Key==`Name`].Value }'

# List Running Instances of a Specific VPC

aws ec2 describe-instances --filters  "Name=instance-state-name,Values=running" Name=vpc-id,Values=YOURVPCID --query 'Reservations[].Instances[].{ID: InstanceId,Hostname: PublicDnsName,Name: Tags[?Key==`Name`].Value }'
################################################################################################

#!/bin/bash

# https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html

# https://aws.amazon.com/premiumsupport/knowledge-center/sftp-iam-user-cli/

1. aws iam create-instance-profile --instance-profile-name Linux-Academy-ECS-Instance-Role

2. cat <<EOF >ec2-trust-relationship.json
{
  "Version": "2008-10-17",
  "Statement": [
    {
      "Sid": "",
      "Effect": "Allow",
      "Principal": {
        "Service": "ec2.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}
EOF

aws iam create-role --role-name Linux-Academy-ECS-Instance-Role --assume-role-policy-document file://ec2-trust-relationship.json --description "EC2 Access"

# Note: Attaching AWS Managed Policy ARN is fixed

3. aws iam attach-role-policy --role-name Linux-Academy-ECS-Instance-Role --policy-arn arn:aws:iam::aws:policy/service-role/AmazonEC2ContainerServiceforEC2Role

aws iam attach-role-policy --role-name Linux-Academy-ECS-Instance-Role --policy-arn arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess

# Add the s3access role to the s3access-profile instance profile.
4. aws iam add-role-to-instance-profile --instance-profile-name Linux-Academy-ECS-Instance-Role --role-name Linux-Academy-ECS-Instance-Role






# Create a keypair

aws ec2 create-key-pair --key-name Linux-Academy --query 'KeyMaterial' --output text > ~/.ssh/Linux-Academy.pem

# Create a s3 bucket

aws s3 mb s3://cloudgeeks.ca-ecs-learning
OR
aws s3api create-bucket --bucket cloudgeeks.ca-ecs-learning

aws s3 cp ecs.config s3://cloudgeeks.ca-ecs-learning/
aws s3 ls s3://cloudgeeks.ca-ecs-learning


aws ec2 run-instances --image-id ami-2b3b6041 --count 1 \
--instance-type t2.micro --iam-instance-profile Name=Linux-Academy-ECS-Instance-Role \
--key-name Linux-Academy --subnet-id subnet-0703816245a8a7457    \
--user-data file://copy-ecs-config-to-s3

# Get EC2 instance status

aws ec2 describe-instance-status --instance-id i-0eb3791217abd83ef

# Verify the EC2 instance is now part of the deepdive cluster

aws ecs list-container-instances --cluster deepdive

# Terminate EC2 instance

 aws ec2 terminate-instances --instance-ids i-0eb3791217abd83ef

#END



# Get the ARN of SSM Policy for IAM Role `AmazonEC2RoleforSSM`

# Note down the ARN of the policy from the following command:

aws iam list-policies --scope AWS --query "Policies[?PolicyName == 'AmazonEC2RoleforSSM']"

# Optionally, you may also use the following command in addition to the value of DefaultVersionId from the above command to look at the JSON document of the policy in question via the CLI:

aws iam get-policy-version --policy-arn <ARN-OF-POLICY> --version-id <VERSION-ID-STRING-FROM-PREV-COMMAND>

# Create IAM Role for EC2 and Assign SSM Policy to It

# Copy the following JSON and create a new JSON file in your current directory. Name it EC2Trust.json:

{
  "Version": "2012-10-17",
  "Statement": {
    "Effect": "Allow",
    "Principal": {"Service": "ec2.amazonaws.com"},
    "Action": "sts:AssumeRole"
  }
}


# Create the role and attach the trust policy JSON file you created above to it. Make sure you execute the following command in the same directory where you created the EC2Trust.json file:

aws iam create-role --role-name MyEC2SSMRole --assume-role-policy-document file://EC2Trust.json

# Assign policy from previous step to the newly created role:

aws iam attach-role-policy --role-name MyEC2SSMRole --policy-arn <SSM-POLICY-ARN>


# Create and Attach an Instance Profile to the IAM EC2 Service Role

# Create instance profile using the command below and note down the name you assign to the instance profile (in the case of the command below, it is MyEC2InstanceProfile). Note down the ARN of the instance profile returned to you from executing the command below. We'll be using it in the next step when we create an EC2 instance.

aws iam create-instance-profile --instance-profile-name MyEC2InstanceProfile

# Add the role created in second task to the instance profile created above:

aws iam add-role-to-instance-profile --instance-profile-name MyEC2InstanceProfile --role-name MyEC2SSMRole


# Gather Necessary Data for Plugging into EC2 Instance Creation Command


# Get subnet ID:

aws ec2 describe-subnets --query "Subnets[?Tags[?Value == 'SubnetA'] ].SubnetId | [0]"

# Get security group ID:

aws ec2 describe-security-groups --filters Name=group-name,Values=SG --query "SecurityGroups[?GroupName == 'SG'].GroupId | [0]"

# Get AMI ID (with SSM installed):

aws ec2 describe-images --filters "Name=architecture,Values=x86_64" "Name=description,Values=*Amazon Linux 2 AMI 2.0.2019*gp2" "Name=owner-id,Values=137112412989" "Name=image-type,Values=machine" --query "sort_by(Images, &CreationDate)[::-1].ImageId | [0]"

# Create an EC2 Instance Using Subnet, Security Group, and AMI ID

# Plug in the subnet ID, security group ID, AMI ID, and instance profile ARN in the following command:

aws ec2 run-instances --associate-public-ip-address --security-group-ids <SECURITY-GROUP-ID> --iam-instance-profile Arn=<INSTANCE-PROFILE-ARN> --instance-type t2.micro --image-id <AMI-ID> --subnet-id <SUBNET-ID> --tag-specifications "ResourceType=instance,Tags=[{Key=Name,Value=MyEC2}]"

# Notice that we are giving our EC2 instance the name MyEC2 (basically we're tagging it with this name) so we can get its instance ID and later confirm that SSM sees it.
# If you gave your IAM instance profile the same name as given in the lab task(i.e. MyEC2InstanceProfile ) , you can fetch the Instance Profile ARN(required by command above), by using the following command:

aws iam get-instance-profile --instance-profile-name MyEC2InstanceProfile

# Confirm via SSM CLI API (or GUI) that the Newly Created EC2 Instance Is Visible to It

# Get the instance ID of the newly created instance (remember we named it MyEC2, so we'll use this name in the command to get its instance ID — if you tagged/named it differently, be sure to use that name):

aws ec2 describe-instances --filters Name=tag:Name,Values=MyEC2 --query "Reservations[].Instances[].InstanceId"

# Run the following SSM instance information API command to see if the same instance ID from the command above is showing up in SSM API's output (plug the instance ID you noted in the previous command into this command):

aws ssm describe-instance-information --query "InstanceInformationList[?InstanceId == '<INSTANCE-ID>']"

# The command should return an object with information about the newly configured EC2 instance with Systems Manager.

# Note: It can take up to five minutes for the instance to show up in the SSM GUI or API command output.

# You can also choose to skip this last step, log in to the AWS Management Console, and compare the EC2 instance value in the EC2 console with the instance ID value under AWS Systems Manager > Managed Instances.