Explore topic-wise InterviewSolutions in Current Affairs.

Some of the possible connection ISSUES with EC2 instance are:

• Connection TIME out
• Permission denied due to host key not found
• Unprotected private key FILE
• Permission denied due to user key not recognized by server
• No supported AUTHENTICATION method available
• Server refused the key AWS Video TRAINING

Some of the possible connection issues with EC2 instance are:

AWS provides an option of creating a Placement Group in EC2 to logically group the instances within as SINGLE Availability Zone.

We get the benefits of low NETWORK latency and high network THROUGHPUT by USING a Placement Group.

Placement Group is a free option as of now. When we stop an instance, it will run in same Placement Group in restart at a later point of time.

The biggest limitation of Placement Group is that we cannot add Instances from multiple availability zones to ONE Placement Group.

AWS provides an option of creating a Placement Group in EC2 to logically group the instances within as single Availability Zone.

We get the benefits of low network latency and high network throughput by using a Placement Group.

Placement Group is a free option as of now. When we stop an instance, it will run in same Placement Group in restart at a later point of time.

The biggest limitation of Placement Group is that we cannot add Instances from multiple availability zones to one Placement Group.

Main features of Application Load Balancer (ALB) are as follows:

• Content-Based Routing: In ALB, we can make use of content in the REQUEST to decide the routing of a request to a specific service.
• HTTP/2: ALB supports the new version of HTTP protocol. In this protocol, we can send multiple requests on same connection. It also supports TLS and HEADER compression.
• WebSockets: ALB supports WebSockets in EC2. With WebSockets, a SERVER can exchange real-time MESSAGES with the end-users.
• Layer-7 Load Balancing: ALB can also load balance HTTP/HTTPS application with layer-7 specific features.
• Delete Protection: ALB also provides Delete Protection option by which we can prevent it from getting deleted by mistake.
• Containerized Application Support: We can use ALB to load balance multiple containers across multiple ports on same EC2 INSTANCE.

Main features of Application Load Balancer (ALB) are as follows:

Some of the main features of Classic Load Balancer (CLB) in Amazon EC2 are as follows:

Health Check: Based on the result of Health Check, Classic Load Balancer can decide to route the traffic. If any instance has unhealthy results, CLB will not route the traffic to that instance.

Security: We can create security groups for CLB in Virtual Private Cloud (VPC). With these features, it is easy to implement secure load balancing within a network.

High Availability: With CLB, we can distribute traffic among EC2 instances in single or multiple Availability Zones. This helps in providing very high scale of availability for the incoming traffic.

Sticky Sessions: CLB also supports sticky session by using cookies. The sticky sessions make sure that the traffic from a USER is ALWAYS routed to the same instance so that user gets seamless experience.

IPv6: CLB also support Internet Protocol version 6.

Operational Monitoring: We can also perform operational monitoring CLB and collect statistics on request count, latency etc. These METRICS can be monitored in CloudWatch.

Some of the main features of Classic Load Balancer (CLB) in Amazon EC2 are as follows:

Health Check: Based on the result of Health Check, Classic Load Balancer can decide to route the traffic. If any instance has unhealthy results, CLB will not route the traffic to that instance.

Security: We can create security groups for CLB in Virtual Private Cloud (VPC). With these features, it is easy to implement secure load balancing within a network.

High Availability: With CLB, we can distribute traffic among EC2 instances in single or multiple Availability Zones. This helps in providing very high scale of availability for the incoming traffic.

Sticky Sessions: CLB also supports sticky session by using cookies. The sticky sessions make sure that the traffic from a user is always routed to the same instance so that user gets seamless experience.

IPv6: CLB also support Internet Protocol version 6.

Operational Monitoring: We can also perform operational monitoring CLB and collect statistics on request count, latency etc. These metrics can be monitored in CloudWatch.

“On-Demand” instances allow the user to use the compute by hour without requiring long TERM commitment. There are no guarantees that the user will always be able to launch SPECIFIC instance TYPES in an availability zone, though AWS tries it’s best to meet the needs. This service is preferable for POCs and they do not suffer an interruption of the service(by AWS) like Spot instances.

“Spot” instances are a bid_for_low_price version of On-Demand instances, but could be SHUT down by AWS anytime the Spot instance price goes HIGHER than bid price. Spot price fluctuates based on the supply and demand of the capacity. It’s essentially the leftover capacity of AWS to be used. There is no difference in the performance compared to On-Demand instances and is usually cheaper than On-demand instances as there is no guarantee provided over the availability. The user can choose a start time and end time for the instances or can make a persistent request(no end time specified) for this service. This service is preferable for computing needs which are not tied to any deadlines, computing needs are large and the interruption of service is acceptable.

“On-Demand” instances allow the user to use the compute by hour without requiring long term commitment. There are no guarantees that the user will always be able to launch specific instance types in an availability zone, though AWS tries it’s best to meet the needs. This service is preferable for POCs and they do not suffer an interruption of the service(by AWS) like Spot instances.

“Spot” instances are a bid_for_low_price version of On-Demand instances, but could be shut down by AWS anytime the Spot instance price goes higher than bid price. Spot price fluctuates based on the supply and demand of the capacity. It’s essentially the leftover capacity of AWS to be used. There is no difference in the performance compared to On-Demand instances and is usually cheaper than On-demand instances as there is no guarantee provided over the availability. The user can choose a start time and end time for the instances or can make a persistent request(no end time specified) for this service. This service is preferable for computing needs which are not tied to any deadlines, computing needs are large and the interruption of service is acceptable.

In AMAZON EC2, we can even bid for getting a COMPUTING instance. Any instance procured by bidding is a Spot Instance. Multiple users bid for an EC2 Instance. Once the bid price EXCEEDS the Spot price, the user with the highest bid gets it. As long as their bid price remains higher than the Spot price, they can KEEP using it.

Spot price varies with the SUPPLY and demand. Once Spot price exceeds Bid price, the instance will be taken back from the user.

In Amazon EC2, we can even bid for getting a computing instance. Any instance procured by bidding is a Spot Instance. Multiple users bid for an EC2 Instance. Once the bid price exceeds the Spot price, the user with the highest bid gets it. As long as their bid price remains higher than the Spot price, they can keep using it.

Spot price varies with the supply and demand. Once Spot price exceeds Bid price, the instance will be taken back from the user.

Xen

Xen

• Stop the instance.
• Detach the root EBS volume.
• ATTACH the alternate EBS volume (as the root e.g. /dev/sda1)
• START the instance.
• This presupposes that your alternate EBS volume is bootable, of course – it has to CONTAIN the bootable OS image.

Rebooting an INSTANCE is like rebooting a PC. The hard disk isn’t affected. You don’t return to the IMAGE’s original state, but the contents of the hard disks are those before the reboot.

Rebooting isn’t associated with billing. Billing starts when you INSTANTIATE an image and stops when you terminate it. Rebooting in between hasn’t any EFFECT.

Rebooting an instance is like rebooting a PC. The hard disk isn’t affected. You don’t return to the image’s original state, but the contents of the hard disks are those before the reboot.

Rebooting isn’t associated with billing. Billing starts when you instantiate an image and stops when you terminate it. Rebooting in between hasn’t any effect.

The BEST way of connecting to your cloud resources (for ex- ec2 INSTANCES) from your own data center (for eg- private cloud) is a VPC. Once you connect your datacenter to the VPC in which your instances are present, each instance is assigned a private IP ADDRESS which can be accessed from your datacenter. Hence, you can access your PUBLIC cloud resources, as if they were on your own NETWORK.

The best way of connecting to your cloud resources (for ex- ec2 instances) from your own data center (for eg- private cloud) is a VPC. Once you connect your datacenter to the VPC in which your instances are present, each instance is assigned a private IP address which can be accessed from your datacenter. Hence, you can access your public cloud resources, as if they were on your own network.

Yes, it can be used for instances with root devices backed by local INSTANCE storage. By using Amazon S3, developers have access to the same highly scalable, reliable, fast, inexpensive data storage infrastructure that Amazon uses to run its own global network of web sites. In order to execute systems in the Amazon EC2 environment, developers use the tools provided to load their Amazon Machine IMAGES (AMIs) into Amazon S3 and to MOVE them between Amazon S3 and Amazon EC2.

Another use case could be for WEBSITES hosted on EC2 to load their static content from S3.

Yes, it can be used for instances with root devices backed by local instance storage. By using Amazon S3, developers have access to the same highly scalable, reliable, fast, inexpensive data storage infrastructure that Amazon uses to run its own global network of web sites. In order to execute systems in the Amazon EC2 environment, developers use the tools provided to load their Amazon Machine Images (AMIs) into Amazon S3 and to move them between Amazon S3 and Amazon EC2.

Another use case could be for websites hosted on EC2 to load their static content from S3.

The PRIMARY private IP address cannot be CHANGED. Secondary private addresses can be unassigned, ASSIGNED or moved between interfaces or instances at any point.

The primary private IP address cannot be changed. Secondary private addresses can be unassigned, assigned or moved between interfaces or instances at any point.

First of all, let’s understand that Spot Instance, On-Demand instance and Reserved Instances are all models for pricing. Moving along, spot instances provide the ability for customers to purchase compute capacity with no upfront commitment, at HOURLY rates usually lower than the On-Demand RATE in each region. Spot instances are just like bidding, the bidding price is CALLED Spot Price.

The Spot Price fluctuates based on supply and demand for instances, but customers will never pay more than the maximum price they have specified. If the Spot Price moves higher than a customer’s maximum price, the customer’s EC2 instance will be shut down automatically.

But the reverse is not true, if the Spot prices come down again, your EC2 instance will not be launched automatically, one has to do that manually. In Spot and On demand instance, there is no commitment for the duration from the USER side, however in reserved instances one has to STICK to the time period that he has chosen.

First of all, let’s understand that Spot Instance, On-Demand instance and Reserved Instances are all models for pricing. Moving along, spot instances provide the ability for customers to purchase compute capacity with no upfront commitment, at hourly rates usually lower than the On-Demand rate in each region. Spot instances are just like bidding, the bidding price is called Spot Price.

The Spot Price fluctuates based on supply and demand for instances, but customers will never pay more than the maximum price they have specified. If the Spot Price moves higher than a customer’s maximum price, the customer’s EC2 instance will be shut down automatically.

But the reverse is not true, if the Spot prices come down again, your EC2 instance will not be launched automatically, one has to do that manually. In Spot and On demand instance, there is no commitment for the duration from the user side, however in reserved instances one has to stick to the time period that he has chosen.

STARTING, stopping and terminating are the three states in an EC2 instance, let’s discuss them in detail:

• Stopping and Starting an instance: When an instance is STOPPED, the instance performs a normal shutdown and then transitions to a stopped state. All of its AMAZON EBS volumes remain attached, and you can start the instance again at a later time. You are not charged for additional instance hours while the instance is in a stopped state.
• Terminating an instance: When an instance is TERMINATED, the instance performs a normal shutdown, then the attached Amazon EBS volumes are deleted unless the volume’s deleteOnTermination attribute is set to false. The instance itself is ALSO deleted, and you can’t start the instance again at a later time.

Starting, stopping and terminating are the three states in an EC2 instance, let’s discuss them in detail:

Amazon EC2 uses public–key cryptography to encrypt and decrypt login information. Public–key cryptography uses a public key to encrypt a PIECE of data, such as a password, then the recipient uses the private key to decrypt the data. The public and private keys are known as a key PAIR.

After configuring the AMI to PREVENT LOGGING in using a password, you must make sure users can log in using another mechanism.

Amazon EC2 uses public–key cryptography to encrypt and decrypt login information. Public–key cryptography uses a public key to encrypt a piece of data, such as a password, then the recipient uses the private key to decrypt the data. The public and private keys are known as a key pair.

After configuring the AMI to prevent logging in using a password, you must make sure users can log in using another mechanism.

Using a fixed root password for a public AMI is a security risk that can quickly become known. Even relying on users to CHANGE the password after the first login opens a small window of opportunity for POTENTIAL abuse.

Following are the steps to DISABLE password-based remote logins for the root user:

Open the /etc/ssh/sshd_config FILE with a TEXT editor and locate the following line:
#PermitRootLogin yes
Change the line to:
PermitRootLogin without-password
The location of this configuration file might differ for your distribution.

Using a fixed root password for a public AMI is a security risk that can quickly become known. Even relying on users to change the password after the first login opens a small window of opportunity for potential abuse.

Following are the steps to disable password-based remote logins for the root user:

Open the /etc/ssh/sshd_config file with a text editor and locate the following line:
#PermitRootLogin yes
Change the line to:
PermitRootLogin without-password
The location of this configuration file might differ for your distribution.

AWS recommends that your AMIs download and UPGRADE the Amazon

EC2 AMI creation tools during startup. This ENSURES that new AMIs based on your SHARED AMIs have the LATEST AMI tools.

For Amazon Linux, add the following to /etc/rc.local:

# Update the Amazon EC2 AMI tools

echo ” + Updating EC2 AMI tools”

yum update -y aws-amitools-ec2

echo ” + Updated EC2 AMI tools”

AWS recommends that your AMIs download and upgrade the Amazon

EC2 AMI creation tools during startup. This ensures that new AMIs based on your shared AMIs have the latest AMI tools.

For Amazon Linux, add the following to /etc/rc.local:

# Update the Amazon EC2 AMI tools

echo ” + Updating EC2 AMI tools”

yum update -y aws-amitools-ec2

echo ” + Updated EC2 AMI tools”

A shared AMI is an AMI that a developer CREATED and made available for other DEVELOPERS to use.

One of the easiest WAYS to get started with Amazon EC2 is to use a shared AMI that has the components you need and then add CUSTOM CONTENT. You can also create your own AMIs and share them with others.

• Use a shared AMI at your own risk. Amazon can’t vouch for the integrity or security of AMIs shared by other Amazon EC2 users. AWS recommends that you get an AMI from a trusted source.

A shared AMI is an AMI that a developer created and made available for other developers to use.

One of the easiest ways to get started with Amazon EC2 is to use a shared AMI that has the components you need and then add custom content. You can also create your own AMIs and share them with others.

• Charges varies upon AMIs backed and storage VOLUMS.
• AMIs backed by instance storage charged for: AMI storage + Instance usage
• AMIs backed by Amazon EBS storage charged for: Volume storage + Usage in addition to the AMI + instance usage
• When an Amazon EBS-backed instance is stopped, you are not charged for instance usage, but you are STILL charged for volume storage.
• AWS charges a full instance hour for EVERY transition from a stopped state to a running state, even if we transition the instance multiple TIMES within a single hour.

For example: if hourly instance charge for your instance is $0.10 and if you were to run that instance for one hour without stopping it, you would be charged $0.10. If you stopped and restarted that instance twice during that hour, then you would be charged $0.30 for that hour of usage (the initial $0.10, PLUS 2 x $0.10 for each restart).

For example: if hourly instance charge for your instance is $0.10 and if you were to run that instance for one hour without stopping it, you would be charged $0.10. If you stopped and restarted that instance twice during that hour, then you would be charged $0.30 for that hour of usage (the initial $0.10, plus 2 x $0.10 for each restart).

All AMIS are categorized as either BACKED by AMAZON EBS or backed by instance store.

Backed by Amazon EBS – means that the root device for an instance launched from the AMI is an Amazon EBS volume created from an Amazon EBS snapshot.

Backed by instance store – means that the root device for an instance launched from the AMI is an instance store volume created from a TEMPLATE stored in Amazon S3.

Root device size limit for –

Amazon EBS – Backed is 16 TiB

Amazon Instance Store-Backed is 10 GiB

All AMIs are categorized as either backed by Amazon EBS or backed by instance store.

Backed by Amazon EBS – means that the root device for an instance launched from the AMI is an Amazon EBS volume created from an Amazon EBS snapshot.

Backed by instance store – means that the root device for an instance launched from the AMI is an instance store volume created from a template stored in Amazon S3.

Root device size limit for –

Amazon EBS – Backed is 16 TiB

Amazon Instance Store-Backed is 10 GiB

We can determine the Root Device type of AMI using FOLLOWING 2 methods.

Method 1: Following are the steps to determine the Root Device type of an AMI using the console

1. Open the Amazon EC2 console
2. In the navigation pane, click AMIS, and SELECT the AMI
3. Check the VALUE of Root Device Type in the DETAILS tab as follows

• If the value is ebs, this is an Amazon EBS-backed AMI
• If the value is instance store, this is an instance store-backed AMI

Method 2: Following are the steps to determine the root device type of an AMI using the command line

We can use one of the following commands.

1. describe-images (AWS CLI)
2. Get-EC2Image (AWS Tools for Windows PowerShell)

We can determine the Root Device type of AMI using following 2 methods.

Method 1: Following are the steps to determine the Root Device type of an AMI using the console

Method 2: Following are the steps to determine the root device type of an AMI using the command line

We can use one of the following commands.

You can customize a instance that is launched from a public AMI and then SAVE that configuration as a custom AMI for your own use.

Instances that you LAUNCH from your AMI use all the CUSTOMIZATIONS that you’ve made.

You can customize a instance that is launched from a public AMI and then save that configuration as a custom AMI for your own use.

Instances that you launch from your AMI use all the customizations that you’ve made.

Key PAIR is used to log in to your instance securely. This is public-key cryptography to SECURE the LOGIN information for your instance.

Key pair is used to log in to your instance securely. This is public-key cryptography to secure the login information for your instance.

We can create one using the Amazon EC2 CONSOLE. To launch instances in MULTIPLE regions, we’ll need to create a key pair in each region.

Following are the steps to create Key Pair:

• Sign in to Amaon Web Service.
• From the AWS dashboard, choose EC2 to open the Amazon EC2 console.
• From the navigation bar, select a region for the key pair.
• In the left navigation PANE, under NETWORK & SECURITY, click Key Pairs.
• Click Create Key Pair.
• Enter a name for the new key pair in the Key pair name field of the Create Key Pair dialog box, and then click Create.
• 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 .pem.

We can create one using the Amazon EC2 console. To launch instances in multiple regions, we’ll need to create a key pair in each region.

Following are the steps to create Key Pair:

AWS 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.

AWS 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.

You can migrate your EC2 instance from one Availability Zone to another.

FOLLOWING are the steps to migrate an Instance to another Availability Zone:

• Create an AMI from the RUNNING instance
• Launch an instance from the AMI that you just created, specify the new Availability Zone
• You can use the same instance type as the original instance, or select a new instance type
• If the original instance has an associated Elastic IP address, then associate it with the new instance
• If the original instance is a Reserved Instance, CHANGE the Availability Zone for your reservation

You can migrate your EC2 instance from one Availability Zone to another.

Following are the steps to migrate an Instance to another Availability Zone:

We can LAUNCH DIFFERENT types of instances from a single AMI. An INSTANCE type essentially determines the hardware of the (pivotal training) host computer used for your instance. Each instance type offers different compute and memory capabilities. 

After we launch an instance, it looks like a TRADITIONAL host, and we can INTERACT with it as we would do with any computer. We have complete control of our instances; we can use sudo to run commands that require root privileges.

We can launch different types of instances from a single AMI. An instance type essentially determines the hardware of the (pivotal training) host computer used for your instance. Each instance type offers different compute and memory capabilities. 

After we launch an instance, it looks like a traditional host, and we can interact with it as we would do with any computer. We have complete control of our instances; we can use sudo to run commands that require root privileges.

An Amazon Machine Image (AMI) is a template that CONTAINS a software configuration (for example, an operating system, an APPLICATION server, and applications). From an AMI, we LAUNCH an instance, which is a copy of the AMI running as a virtual server in the cloud. We can EVEN launch MULTIPLE instances of an AMI.

An Amazon Machine Image (AMI) is a template that contains a software configuration (for example, an operating system, an application server, and applications). From an AMI, we launch an instance, which is a copy of the AMI running as a virtual server in the cloud. We can even launch multiple instances of an AMI.

Amazon WEB SERVICES provides several ways to access Amazon EC2, like web-based INTERFACE, AWS Command Line Interface (CLI) and Amazon Tools for Windows Powershell. First, you need to SIGN up for an AWS account and you can access Amazon EC2.

Amazon EC2 provides a Query API. These requests are HTTP or HTTPS requests that use the HTTP verbs GET or POST and a Query parameter named Action.

Amazon Web Services provides several ways to access Amazon EC2, like web-based interface, AWS Command Line Interface (CLI) and Amazon Tools for Windows Powershell. First, you need to sign up for an AWS account and you can access Amazon EC2.

Amazon EC2 provides a Query API. These requests are HTTP or HTTPS requests that use the HTTP verbs GET or POST and a Query parameter named Action.

To GET the maximum benefit from and satisfaction with Amazon EC2.

There are mainly four BEST practices:

• Security and Network Best Practices
• Storage
• Resource MANAGEMENT
• Backup and Recovery

To get the maximum benefit from and satisfaction with Amazon EC2.

There are mainly four best practices:

After we are finished with the INSTANCE we CREATED, we can clean up by terminating the instance.

Following are the steps to terminate the EC2 instance:

• In the navigation pane, choose Instances. In the list of instances, select the instance.
• Choose Actions, then Instance STATE, and then choose Terminate.
• Choose Yes,Terminate when prompted for CONFIRMATION.

After we are finished with the instance we created, we can clean up by terminating the instance.

Following are the steps to terminate the EC2 instance:

We can attach an EBS volume to one of our INSTANCES that is in the same Availability ZONE as the Volume.

Following are the steps to attache an EBS volumn to an instance using console:

• Open the Amazon EC2 console.
• In the left NAVIGATION pane, choose Volumes.
• SELECT a volume and choose Attach Volume.
• Select the instance to which you want to attach the volume.
• Click on Attach.
• Now connect to your instance and make the volume AVAILABLE.

We can attach an EBS volume to one of our instances that is in the same Availability Zone as the Volume.

Following are the steps to attache an EBS volumn to an instance using console:

There are several ways to connect to a Linux instance. One of the commonly USED method is to connect Linux instance from Windows local machine using PuTTY.

Following are the steps to connect to a Linux instance:

• Install PuTTY on your local machine.
• Get your instance ID.
• Get the public DNS name of the instance.
• Locate the PRIVATE key.
• Enable inbound SSH traffic from your IP ADDRESS to your instance.
• Converting Your Private Key Using PuTTYgen.
• STARTING a PuTTY Session.
• Now you are connected to your EC2 instance.

There are several ways to connect to a Linux instance. One of the commonly used method is to connect Linux instance from Windows local machine using PuTTY.

Following are the steps to connect to a Linux instance:

We can launch Linux/Windows Amazon EC2 instance using AWS Management Console.

Following are the steps to create Amazon EC2 instance:

• Open the Amazon EC2 console.
• From the console dashboard, choose Launch Instance.
• Choose an Amazon Machine IMAGE (AMI).
• Choose an Instance Type.
• Click on Review and Launch to let the wizard COMPLETE the other configuration setting.
• On the Review Instance Launch page, under Security GROUPS select a Security Group.
• Click on Launch on the Review Instance Launch.
• Select an Existing ket pair when it PROMPTE for key pair.
• Click on View Instance to return on the console to see instance is launching.

We can launch Linux/Windows Amazon EC2 instance using AWS Management Console.

Following are the steps to create Amazon EC2 instance:

We can create Security GROUP in Amazon EC2 using the Amazon EC2 console. To LAUNCH instances in multiple regions, we’ll need to create a Security Group in each region.

FOLLOWING are the steps to create Security Group in Amazon EC2:

• Open the Amazon EC2 console.
• From the left navigation bar, select a region for the security group.
• Click Security Groups in the navigation pane.
• Click Create Security Group.
• Enter a name for the new security group and a description.
• In the VPC list, select your VPC.
• On the INBOUND tab, click Add RULE for each new rule, and then click Create.

We can create Security Group in Amazon EC2 using the Amazon EC2 console. To launch instances in multiple regions, we’ll need to create a Security Group in each region.

Following are the steps to create Security Group in Amazon EC2:

FOLLOWING are the features of the Security Group in Amazon EC2:

• We can add RULES to a security group that enable us to connect to our instance from our IP address using SSH.
• We can ALSO add rules that allow INBOUND and outbound HTTP and HTTPS access from anywhere.

Following are the features of the Security Group in Amazon EC2:

Security GROUPS ACT as a firewall for associated instances, controlling both INBOUND and outbound TRAFFIC at the instance level.

Security groups act as a firewall for associated instances, controlling both inbound and outbound traffic at the instance level.

By default, the root device volume for an AMI backed by Amazon EBS is deleted when the instance terminates. To change the default behavior, set the DeleteOnTermination attribute to FALSE using a block device mapping.

• To change the root device volume of an instance to persist at launch using the console
• Open the Amazon EC2 console.
• From the Amazon EC2 console DASHBOARD, click Launch Instance.
• On the Choose an Amazon Machine Image (AMI) page, choose the AMI to use and click Select.
• FOLLOW the wizard to complete the Choose an Instance Type and Configure Instance Details PAGES.
• On the Add Storage page, deselect the Delete On Termination CHECK box for the root volume.
• Complete the remaining wizard pages, and then click Launch.
• Changing the Root Volume of an Instance to Persist Using the AWS CLI
• Use the run-instances command to preserve the root volume by including a block device mapping that sets its DeleteOnTermination attribute for to false.

By default, the root device volume for an AMI backed by Amazon EBS is deleted when the instance terminates. To change the default behavior, set the DeleteOnTermination attribute to false using a block device mapping.

When you launch an instance, the ROOT Device Volume contains the image USED to boot the instance.

You can launch an instance from one of two types of AMIs:

1. Instance store-backed AMI
2. EBS BASED storage

When you launch an instance, the Root Device Volume contains the image used to boot the instance.

You can launch an instance from one of two types of AMIs:

Each region is completely independent and each Availability Zone is isolated. When you view your resources, you’ll only SEE the resources tied to the region you have specified.

To launch a EC2 instance, you must SELECT an AMI that’s in the same region (if the AMI is in ANOTHER region then you can copy the AMI to the region you are using). Now select an Availability Zone or LET AWS choose for you. After creating the EC2 instance, it will show up in selected Availability Zone.

Each region is completely independent and each Availability Zone is isolated. When you view your resources, you’ll only see the resources tied to the region you have specified.

To launch a EC2 instance, you must select an AMI that’s in the same region (if the AMI is in another region then you can copy the AMI to the region you are using). Now select an Availability Zone or let AWS choose for you. After creating the EC2 instance, it will show up in selected Availability Zone.

Amazon EC2 is hosted in multiple LOCATIONS world-wide. These locations are composed of regions and AVAILABILITY ZONES. Each region is a separate geographic area. Each region has multiple, isolated locations known as Availability Zones.

Each region is completely INDEPENDENT. Each Availability Zone is isolated, but the Availability Zones in a region are connected through low-latency LINKS. The following diagram illustrates the relationship between regions and Availability Zones.

Amazon EC2 is hosted in multiple locations world-wide. These locations are composed of regions and Availability Zones. Each region is a separate geographic area. Each region has multiple, isolated locations known as Availability Zones.

Each region is completely independent. Each Availability Zone is isolated, but the Availability Zones in a region are connected through low-latency links. The following diagram illustrates the relationship between regions and Availability Zones.

Yes, it can be cast-off for instances with root approaches backed by native occurrence storage. By using Amazon S3, developers have access to the similar EXTREMELY scalable, dependable, FAST, low-priced data storage substructure that Amazon uses to track its own worldwide network of web sites. In order to perform SYSTEMS in the Amazon EC2 atmosphere, developers use the tools providing to load their Amazon Machine IMAGES (AMIs) into Amazon S3 and to transfer them between Amazon S3 and Amazon EC2. Additional use case MIGHT be for websites hosted on EC2 to load their stationary content from S3

Yes, it can be cast-off for instances with root approaches backed by native occurrence storage. By using Amazon S3, developers have access to the similar extremely scalable, dependable, fast, low-priced data storage substructure that Amazon uses to track its own worldwide network of web sites. In order to perform systems in the Amazon EC2 atmosphere, developers use the tools providing to load their Amazon Machine Images (AMIs) into Amazon S3 and to transfer them between Amazon S3 and Amazon EC2. Additional use case might be for websites hosted on EC2 to load their stationary content from S3

Amazon EC2 offers numerous data storage choices for your occurrences. Each choice has an exclusive mixture of presentation and sturdiness. These storages can be used self-sufficiently or in grouping to suit your NECESSITIES.

There are chiefly four types of storages offered by AWS:

• Amazon EBS: Its sturdy, block-level storage capacities can involve in running Amazon EC2 occurrence. The Amazon EBS volume continues self-sufficiently from the running lifespan of an Amazon EC2 occurrence. After an EBS volume is involved to an example, you can use it like any other bodily hard drive. Amazon EBS encryption feature provisions encryption feature.
• Amazon EC2 Instance Store: Storage disk that is involved to the host computer is mentioned to as occurrence store. The instance storage offers provisional block-level storing for Amazon EC2 instances. The data on an illustration store volume perseveres only during the life of the related Amazon EC2 instance; if you halt or dismiss an instance, any data on occurrence store volumes is misplaced.
• Amazon S3: Amazon S3 delivers access to dependable and budget data storage ORGANIZATION. It is INTENDED to make web-scale calculating SIMPLER by permitting you to store and save any amount of data, at any PERIOD, from within Amazon EC2 or anyplace on the web.
• Addition Storage: Every time your presentation an occurrence from an AMI, a root storage device is twisted for that occurrence. The root storage device comprises all the information essential to boot the occurrence. You can stipulate storage volumes in calculation to the root device volume when you generate an AMI or present an instance using hunk device mapping.

Amazon EC2 offers numerous data storage choices for your occurrences. Each choice has an exclusive mixture of presentation and sturdiness. These storages can be used self-sufficiently or in grouping to suit your necessities.

There are chiefly four types of storages offered by AWS:

As the Amazon EC2 service is a cloud facility so it has ENTIRELY all the cloud features. Amazon EC2 delivers the subsequent features:

• Virtual computing atmosphere (popular as instances)
• Pre-configured patterns for your illustrations (popular as Amazon Machine Images – AMIs)
• Amazon Machine Images known as AMIs is a comprehensive set that you require for your server (counting the operating SYSTEM and extra software)
• Amazon EC2 delivers numerous arrangements of Storage, CPU, memory, and networking measurements for your occurrences (popular as instance type)
• Locked login data for your cases by means of key pair (AWS supplies the public vital and you can SUPPLY the inaccessible key in a safe place)
• Storage capacities of provisional data is ERASED when you stop or dismiss your occurrence (popular as occurrence store volumes)
• Amazon EC2 delivers tenacious storage volumes (by means of Amazon Elastic Block Store – EBS)
• A firewall that permits you to stipulate the procedures, docks, and source IP ranges that can spread your occurrences using security groups
• Stationary IP addresses for lively cloud computing (popular as Elastic IP address)
• Amazon EC2 delivers metadata (popular as tags)
• Amazon EC2 offers virtual systems that are reasonably secluded from the rest of the AWS cloud, and that you can optionally attach to your own system (recognized as virtual PRIVATE clouds – VPCs)

As the Amazon EC2 service is a cloud facility so it has entirely all the cloud features. Amazon EC2 delivers the subsequent features:

Stopping and Starting an instance: When an instance is stopped, the instance performs a normal shutdown and then transitions to a stopped state. All of its Amazon EBS volumes remain attached, and you can START the instance again at a LATER time. You are not charged for additional instance hours while the instance is in a stopped state.

Terminating an instance: When an instance is terminated, the instance performs a normal shutdown, then the attached Amazon EBS volumes are deleted unless the VOLUME’s deleteOnTermination attribute is SET to false. The instance itself is also deleted, and you can’t start the instance again at a later time.

Stopping and Starting an instance: When an instance is stopped, the instance performs a normal shutdown and then transitions to a stopped state. All of its Amazon EBS volumes remain attached, and you can start the instance again at a later time. You are not charged for additional instance hours while the instance is in a stopped state.

Terminating an instance: When an instance is terminated, the instance performs a normal shutdown, then the attached Amazon EBS volumes are deleted unless the volume’s deleteOnTermination attribute is set to false. The instance itself is also deleted, and you can’t start the instance again at a later time.

Amazon EC2 provides many data storage options for your instances. Each option has a unique combination of performance and durability. These storages can be used independently or in combination to suit your requirements.

There are mainly four types of storages PROVIDED by AWS:

• Amazon EBS: Its durable, block-level storage volumes can attached in running Amazon EC2 instance. The Amazon EBS volume persists independently from the running life of an Amazon EC2 instance. After an EBS volume is attached to an instance, you can use it like any other physical hard drive. Amazon EBS ENCRYPTION feature supports encryption feature.
• Amazon EC2 Instance Store: Storage disk that is attached to the host computer is referred to as instance store. The instance storage provides temporary block-level storage for Amazon EC2 instances. The data on an instance store volume persists only (sap TRAINING) during the life of the associated Amazon EC2 instance; if you stop or terminate an instance, any data on instance store volumes is lost.
• Amazon S3: Amazon S3 provides access to reliable and inexpensive data storage infrastructure. It is designed to make web-scale computing easier by enabling you to store and retrieve any AMOUNT of data, at any time, from within Amazon EC2 or anywhere on the web.
• Adding Storage: Every time you launch an instance from an AMI, a root storage device is created for that instance. The root storage device contains all the information necessary to boot the instance. You can specify storage volumes in addition to the root device volume when you create an AMI or launch an instance using block device mapping.

Amazon EC2 provides many data storage options for your instances. Each option has a unique combination of performance and durability. These storages can be used independently or in combination to suit your requirements.

There are mainly four types of storages provided by AWS:

For secure Amazon EC2 best practices, follow the following steps:

• Use AWS identity and access management to control access to your AWS resources
• Restrict access by allowing only trusted HOSTS or networks to access ports on your instance
• Review the rules in your security groups regularly
• Only open up permissions that your require
• DISABLE password-based login, for instance, launched from your AMI Complete Amazon Web SERVICES TUTORIALS

For secure Amazon EC2 best practices, follow the following steps:

As the Amazon EC2 SERVICE is a cloud service so it has all the cloud features.

Amazon EC2 provides the following features:

• Virtual computing environment (known as instances)
• Pre-configured templates for your instances (known as Amazon MACHINE Images – AMIs)
• Amazon Machine Images (AMIs) is a complete package that you need for your server (including the operating system and additional software)
• Amazon EC2 provides various configurations of CPU, memory, storage and networking capacity for your instances (known as instance type)
• Secure login information for your instances using key pairs (AWS stores the public key and you can store the private key in a secure place)
• Storage volumes of temporary data is deleted when you stop or terminate your instance (known as instance store volumes)
• Amazon EC2 provides persistent storage volumes (using Amazon Elastic Block Store – EBS)
• A firewall that enables you to specify the PROTOCOLS, ports, and source IP ranges that can reach your instances using security groups
• Static IP addresses for dynamic cloud computing (known as Elastic IP address)
• Amazon EC2 provides metadata (known as tags)
• Amazon EC2 provides virtual networks that are logically isolated from the rest of the AWS cloud, and that you can optionally (Salesforce Certification Training) connect to your own network (known as virtual private clouds – VPCs)

As the Amazon EC2 service is a cloud service so it has all the cloud features.

Amazon EC2 provides the following features:

AMAZON Elastic Compute Cloud (Amazon EC2) is a Amazon WEB service that provides resizable (scalable) computing capacity in the cloud. You can use Amazon EC2 to launch as many VIRTUAL SERVERS you need. In Amazon EC2 you can CONFIGURE security and networking as well as manage storage.Amazon EC2 service also helps in obtaining and configuring capacity using minimal friction.

Amazon Elastic Compute Cloud (Amazon EC2) is a Amazon web service that provides resizable (scalable) computing capacity in the cloud. You can use Amazon EC2 to launch as many virtual servers you need. In Amazon EC2 you can configure security and networking as well as manage storage.Amazon EC2 service also helps in obtaining and configuring capacity using minimal friction.