Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Amazon EC2 Cookbook
  • Table Of Contents Toc
Amazon EC2 Cookbook

Amazon EC2 Cookbook

By : Sekhar Reddy
Buy this Book
close
close
Amazon EC2 Cookbook

Amazon EC2 Cookbook

By: Sekhar Reddy
Buy this Book

Overview of this book

Discover how to perform a complete forensic investigation of large-scale Hadoop clusters using the same tools and techniques employed by forensic experts. This book begins by taking you through the process of forensic investigation and the pitfalls to avoid. It will walk you through Hadoop’s internals and architecture, and you will discover what types of information Hadoop stores and how to access that data. You will learn to identify Big Data evidence using techniques to survey a live system and interview witnesses. After setting up your own Hadoop system, you will collect evidence using techniques such as forensic imaging and application-based extractions. You will analyze Hadoop evidence using advanced tools and techniques to uncover events and statistical information. Finally, data visualization and evidence presentation techniques are covered to help you properly communicate your findings to any audience.
Table of Contents (10 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Sections
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Selecting and Configuring Amazon EC2 Instances
chevron up
Icon
1. Selecting and Configuring Amazon EC2 Instances
Icon
Introduction
Icon
Choosing the right AWS EC2 instance types
Icon
Preparing AWS CLI tools
Icon
Launching EC2 instances using EC2-Classic and EC2-VPC
Icon
Allocating Elastic IP addresses
Icon
Creating an instance with multiple NIC cards and a static private IP address
Icon
Selecting the right storage for your EC2 instance
Icon
Creating tags for consistency
Icon
Configuring security groups
Icon
Creating an EC2 key pair
Icon
Grouping EC2 instances using placement groups
Icon
Configuring Elastic Load Balancing
Icon
Architecting for high availability
Icon
Creating instances for AWS Marketplace
2
2. Configuring and Securing a Virtual Private Cloud
Icon
2. Configuring and Securing a Virtual Private Cloud
Icon
Introduction
Icon
Creating and configuring VPC
Icon
Configuring VPC DHCP options
Icon
Configuring networking connections between two VPCs (VPC peering)
Icon
Connecting on-premise network to VPC using VPN
3
3. Managing AWS Resources Using AWS CloudFormation
Icon
3. Managing AWS Resources Using AWS CloudFormation
Icon
Introduction
Icon
Creating CloudFormation templates
Icon
Creating CloudFormation templates from existing AWS resources
Icon
Deploying applications on EC2 instances
Icon
Updating a stack
4
4. Securing Access to Amazon EC2 Instances
Icon
4. Securing Access to Amazon EC2 Instances
Icon
Introduction
Icon
Creating IAM users
Icon
Creating IAM groups and assigning group-level permissions
Icon
Creating IAM roles
Icon
Connecting on-premise AD to AWS IAM
Icon
Configuring AWS multifactor authentication
5
5. Monitoring Amazon EC2 Instances
Icon
5. Monitoring Amazon EC2 Instances
Icon
Introduction
Icon
Collecting EC2 metrics using AWS CloudWatch
Icon
Collecting custom metrics from EC2 instances
Icon
Monitoring costs using CloudWatch
Icon
Sending an e-mail based on a CloudWatch alarm
Icon
Using CloudWatch Logs
6
6. Using AWS Data Services
Icon
6. Using AWS Data Services
Icon
Introduction
Icon
Using Amazon SimpleDB services from a Java program
Icon
Using Amazon DynamoDB
Icon
Using Amazon ElastiCache
Icon
Using Amazon RDS
7
7. Accessing Other AWS Services
Icon
7. Accessing Other AWS Services
Icon
Introduction
Icon
Configuring Route 53
Icon
Accessing AWS S3 from applications
Icon
Accessing AWS SES from applications
Icon
Accessing AWS SNS from applications
Icon
Accessing AWS SQS from applications
8
8. Deploying AWS Applications
Icon
8. Deploying AWS Applications
Icon
Introduction
Icon
Using Docker containers for AWS deployments
Icon
Using Chef for AWS deployments
Icon
Using Puppet for AWS deployments
9
Index
Icon
Index

Launching EC2 instances using EC2-Classic and EC2-VPC

Your EC2 instance receives a private IP address from the EC2-Classic range each time it's started, whereas your instance receives a static private IP address from the address range in EC2-VPC. You can only have one private IP address in EC2-Classic, but in EC2-VPC, we have multiple private IP addresses. If you attach an EIP (Elastic IP) to EC2-Classic instance, it will get dissociated when you stop the instance. But for VPC EC2 instance, it remains associated even after you stop it. We can create subnets, routing tables, and Internet gateways in VPC. For on-premise connectivity, we need VPC.

Note

There are different VPC options available, depending on whether you created your AWS account before or after 2013-12-04.

If you created your AWS account after 2013-12-04, then only EC2-VPC is supported. In this case, a default VPC is created in each AWS region. Therefore, unless you create your own VPC and specify it when you launch an instance, your instances are launched in your default VPC.

If you created your AWS account before 2013-03-18, then both EC2-Classic and EC2-VPC are supported in the regions you used before, and only EC2-VPC in regions that you didn't use. In this case, a default VPC is created in each region in which you haven't created any AWS resources. Therefore, unless you create your own VPC and specify it when you launch an instance in a region (that you haven't used before), the instance is launched in your default VPC for that region. However, if you launch an instance in a region that you've used before, the instance is launched in EC2-Classic.

In this recipe, we will launch EC2 instances using EC2-Classic and EC2-VPC.

Getting started…

Before we launch the EC2 instances, we need the image ID.

Run the following command to get the list of images. We can apply the filter to identify a specific image. Record the image ID for later use:

$ aws ec2 describe-images
--filter [Filter]

Note

You can specify one or more filters in this command.

By executing the following command, you obtain the image ID of a 64-bit version of Ubuntu 12.04 image:

$ aws ec2 describe-images
--filter
"Name=virtualization-type,Values=paravirtual"
"Name=root-device-type,Values=ebs" "Name=architecture,Values=x86_64"
"Name=name,Values=ubuntu/images/ebs/ubuntu-precise-12.04-amd64-server-20130204"

How to do it…

We will see the EC2 instances being launched, one by one:

Launching the EC2 instance in EC2-Classic

Using the following command, we can launch instances in EC2-Classic. You can specify the number of instances to launch using the count parameter.

$ aws ec2 run-instances 
--image-id [ImageId] 
--count [InstanceCount] 
--instance-type [InstanceType] 
--key-name [KeyPairName] 
--security-group-ids [SecurityGroupIds]

The parameters used in this command are described as follows:

  • [ImageId]: This is the ID of the image
  • [InstanceCount]: This gives number of instances to be created
  • [InstanceType]: This gives the type of EC2 instance
  • [KeyPairName]: This parameter provides the key/pair name for authentication
  • [SecurityGroupIds]: This one provides security group IDs

The following command will create a micro instance in EC2-Classic (in the Singapore region):

$ aws ec2 run-instances 
--image-id ami-7e2c612c 
--count 1 
--instance-type t1.micro 
--key-name WebServerKeyPair 
--security-group-ids sg-ad70b8c9

Launching the EC2 instance in VPC

Run the following command to launch instances in EC2-VPC. We need to specify the subnet ID while creating an instance in EC2-VPC. Before creating the instance in EC2-VPC, you have to create the VPC and subnets inside it.

$ aws ec2 run-instances 
--image-id [ImageId] 
--count [InstanceCount] 
--instance-type [InstanceType] 
--key-name [KeyPairName] 
--security-group-ids [SecurityGroupIds]
--subnet-id [SubnetId]

Here, SubnetId specifies the subnet where you want to launch your instance.

Next, run the following command to create a micro instance in EC2-VPC (in the Singapore region):

$ aws ec2 run-instances 
--image-id ami-7e2c612c 
--count 1 
--instance-type t1.micro 
--key-name WebServerKeyPair
--security-group-ids sg-ad70b8c8 
--subnet-id subnet-aed11acb

See also

  • The Configuring security groups and Creating an EC2 key pair recipes
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Amazon EC2 Cookbook
End of Section 1
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon