Newvem

Introducing the AWS Utilization Heat Map by Newvem

Cameron Peron — Tue, 12 Mar 2022 12:57:36 +0000

Newvem is proud to announce the public release of our latest feature - the AWS Utilization Heat Map.

Did you know that more than 15% of AWS clouds are underutilized? That’s more than $30M of the $200M in EC2 spend that Newvem has analyzed over the past year! What a waste!

Newvem’s Utilization Heat Map gives you a quick glance into your AWS cloud’s utilization, enabling you to monitor your utilization over the last 30 days, across regions and availability zones, business activities and more.

The heat map is a new feature within Newvem Cloud Care free and premium editions. Both free and premium Newvem Cloud Care users use the heat map to:

Make optimal capacity planning decisions
Visualize their AWS utilization by time series, machine type, region, and availability zone
Identify consistent usage and move it to a cheaper plan (such as Reserved Instances, hybrid or private clouds)
Increase utilization / scale up to meet peak hour demand
Reduce AWS total cost of ownership (TCO)

Here’s an example of variable usage of an e-commerce site operating in US-East:

Already a Newvem Cloud Care user? Log into your account today to see your AWS utilization heat map covering the last 30 days. You can access your heat map by pressing “Utilization Heat Map” on the left hand navigation menu.

Not using Newvem? Sign up for a free Newvem Cloud Care account for powerful AWS health tracking, issue diagnosis, the Utilization Heat Map, and much more!

Why a heat map? Our customers have been asking for an easier way to comprehensively visualize their utilization as it’s next to impossible with AWS tools. The heat map is an intuitive approach that gives a clear picture of where usage is variable (darker in nature) vs. steady (as lighter colors represent the minimum utilization levels) as can be seen in the use case I mentioned above. In contrast to studying and trying to figure this out with spreadsheets, the heat map gives the full picture in one glance as well as a starting point for deeper investigation into improving cloud utilization.

Why is it important?

The Heat Map helps to make better capacity planning decisions, spot variable and steady workloads to better meet workload service levels, and reduce long term costs.
Poor AWS usage creates waste. An average AWS user wastes more than 25% of their spend, while 15% suffer from underutilization issues.
The Capacity Heat Map is the first AWS usage heat map on the market and is FREE for all AWS users.

Why should an AWS user consider this from Newvem?

Newvem is the leader in cloud operations analytics, having analyzed more than $200M in EC2 Spend and $400M in total AWS spend.
Utilization Heat Map helps to solve tactical cost spiral and improve strategic workflow throughput with both Newvem’s free and premium features.
Newvem offers a free service that addresses and helps solve threats related to cloud costs, availability, security, and utilization.

Sign up for free:

About the Author

Cameron Peron is VP Marketing at Newvem. Prior to this, he led the go to market strategy and execution behind several successful startups, including BIScience and Matomy Media. Contact him: [email protected] or on twitter: @cameronperon

Keywords: utilization heat map, cloud map, aws heat map, aws console, aws pricing, reserved instances, aws analytics, aws cloud heat map, aws utilization, aws consumption, cloud capacity

How to Disable or Delete a CloudFront Distribution

Newvem Community — Tue, 05 Mar 2022 17:52:31 +0000

AWS CloudFront is a content distribution service offered by AWS to serve low latency content with high data speed. In CloudFront, the content is organized into distributions and any request to the distribution is automatically served from the nearest edge locations. There are two types of distributions with CloudFront: (1) Download Distribution and (2) Streaming Distribution. The CloudFront distribution cannot be deleted if it is enabled. It is required to first disable the distribution before deleting. During the distribution creation stage, the CloudFront distribution will be in “In Progress” state (Creation in progress state) and the user cannot delete the distribution during that state. When a distribution is deleted, it will take some time (10-15 Minutes) to cascade all the changes to the CloudFront database.

The present guide demonstrates how to disable and delete the existing CloudFront download distribution.

1. Go to the AWS console through http://aws.amazon.com/console. Click on CloudFront.

2. The CloudFront console lists all the available distributions. It displays all the enabled as well as the disabled distributions. It lists the domain name of each distribution as well as the distribution type (streaming / download). Click the icon [i] of any distribution marked in the image or select one of the distributions.

3. Click on the “Disable” button to disable the distribution first.

4. AWS will ask for the confirmation before deleting the distribution. Click on “Yes, Disable”.

5. The process for disabling the distribution will now start. The process may take about 15 minutes to complete. Click on the “Close” button to close the dialogue.

6. CloudFront can serve content from a distribution only if it is enabled. Once disabled, CloudFront will not accept the end user requests for the content from that distribution.

7. The distribution can be deleted only when it is disabled. Select the distribution disabled in step#5 and click on the “Delete” button.

8. AWS will confirm before deleting the distribution. Click on “Yes, Delete”.

9. The distribution will now be deleted.

Keywords: Amazon Web Services, AWS, Amazon AWS Console, AWS S3, Amazon CloudFront, AWS CloudFront, CloudFront, AWS EC2, AWS ELB, CDN, Content Delivery Network

How to List, View and Update an AWS CloudFront Distribution

Newvem Community — Tue, 05 Mar 2022 17:11:41 +0000

AWS Cloudfront is a content distribution service offered by AWS to speed up the distribution of static content, such as media files, html, js, css, etc. Cloudfront serves its content through edge locations. In Cloudfront, the content is organized into distributions. There are two types of distributions with CloudFront: (1) Download CloudFront Distribution and (2) Streaming Distribution. When the user updates the configuration distribution, all the changes are propagated to all the edge locations. Until all the edge locations are updated with the changes, Cloudfront continues to serve the content from the previous distribution.

The present guide demonstrates how to view and update the existing Cloudfront download distribution.

1. Go to the AWS console through http://aws.amazon.com/console. Click on CloudFront.

2. The Cloudfront console lists all the available distributions.. It displays all the enabled as well as the disabled distributions. It lists the domain name of each distribution as well as the distribution type (streaming / download). Click the icon [i] of any distribution marked in the image or select one of the distributions and click on “Distribution Settings”.

3. The distribution settings view has multiple tabs. The General tab displays the following information:

a. Distribution ID: The unique ID associated with the distribution.
b. Domain name: The ID used to access the Cloudfront distribution. For streaming it will start with ‘s’, while for download it will start with ‘d’.
c. The Distribution Delivery Method: Download or Streaming.
d. Price Class: The price specified by the user as the maximum price, which the user is ready to pay for Cloudfront. Based on the selection, Cloudfront will deliver the object from the specific region.
e. CNAME: Allows the user to use URLs for objects instead of the domain name that CloudFront assigns i.e. instead of the Cloudfront distribution http://d111111abcdef8.cloudfront.net/ , the user can specify the custom URL.
f. Cookie Logging is used to allow origins other than AWS S3.
g. Comment is used to describe the distribution.
h. Distribution State when enabled allows Cloudfront to process requests as soon as the distribution is created.
i. Default Root Object serves the default root object when the user requests the root URL of the distribution (i.e. user sends request as http://mynvm.com instead of http://mynvm.com/index.html and gets the object specified as Default Root).
j. If logging is enabled, it shows the logging related information.

4. Click on the Origins tab, which lists the values for the origin. The origin specifies a location where the media file is stored and served from. Cloudfront copies the file from the origin to the edge location to reduce latency and provide faster access to the object. The origin for the download distribution can be AWS S3 or the AWS Services, such as EC2, ELB or the user’s own origin. The OriginID is the ID used to uniquely identify the origin.

5. Click on the Behaviors tab, which lists the cache behavior settings. The fields of the cache behaviors settings are:

a. Path pattern is used to apply the cache behavior to specific objects. If default (*) is selected it will forward all the requests to the bucket displayed under Origin.
b. Viewer Protocol Policy allows the end user to access objects through HTTP and HTTPS.
c. Forward Query string is used to receive different versions of the object based on a query string in the URL.

6. To update the General configuration of the existing distribution, select the General Tab and click on the “Edit” tab.

7. Update the configuration values, as specified in step #3 and then click on “Yes, Edit”.

8. To update the Origins configuration, select the “Origins” tab and click on the “Edit” button.

9. Update the origin domain name and bucket access policy if required. Click on “Yes, Edit” to save the changes.

10. Once all the changes have been applied it may take about 10-15 minutes to update the configuration across all the edge locations.

Keywords: Amazon Web Services, AWS, Amazon AWS Console, AWS S3, Amazon CloudFront, AWS CloudFront, CloudFront, AWS EC2, AWS ELB, CDN, EC2, S3, CDN Edge Location, Content Delivery Network

How to Create an AWS CloudFront Streaming Distribution (and Stream Media Using a JW Player)

Newvem Community — Tue, 05 Mar 2022 15:58:27 +0000

AWS CloudFront is a content distribution service offered by AWS to speed up the distribution of static content, such as media files, html, js, css, etc. CloudFront serves its content through edge locations. As of Dec 2021, AWS had more than 35+ edge locations across the globe. When the user requests for any static content from CloudFront, it will find the nearest edge location to the user and deliver the content from that edge location to reduce the latency.

CloudFront can stream media file using Adobe Real-Time Messaging Protocol (RTMP). The streaming file needs to be on AWS S3 and cannot be served from any other origin.

The present guide demonstrates how to create the CloudFront streaming distribution and stream media using the JW Player.

For streaming the media file, the user needs to provide two types of files: 1) Media file and 2) Media Player file, such as JW Player, Flowplayer or Adobe Flash. The end user will see the media content provided from CloudFront using the media player files provided. The media player file should be uploaded to the AWS S3 bucket and distributed using the download distribution.

1. Create a bucket with AWS S3. Make the bucket publicly accessible with the access policy.

2. Upload the media (video) file to be distributed using CloudFront to the bucket and make it public.

3. Download the Media Player to play the video file uploaded in step#2. The present guide uses the JW Player to stream the video. Download the JW Player from http://www.longtailvideo.com/players.

4. The user can create a separate bucket for the media player. The present guide uses the same bucket for the video file as well as for the media player. Upload the following JW Player files to the AWS Bucket.

a. jwplayer.flash.swf
b. jwplayer.html5.js
c. jwplayer.js

5. Create a download distribution for the bucket created in step #1. The above mentioned download distribution is for the media player files. If the media player files are in some other bucket than specified in step #1, create a distribution for that bucket.

6. Go to the AWS console through http://aws.amazon.com/console. Click on CloudFront and go to the CloudFront console. In the CloudFront console click on “Create Distribution”.

7. In the Create Distribution wizard, select the streaming distribution. Click on “Continue”.

8. Provide the values for the streaming distribution settings. Provide the origin ID as the bucket name created in step #1. The other configuration settings are as follows:

a. Restrict S3 Bucket Access: This is used if the user wants the end users to access objects in an Amazon S3 bucket by using only the CloudFront URLs and not directly through the Amazon S3 URLs.
b. Restrict User Access: Allows everyone to view the content using the public URL.
c. Price Class: Allows the user to select the maximum price, which the user is ready to pay for the CloudFront service.
d. CNAMEs: Allows the user to use the URLs for objects instead of the domain name that CloudFront assigns i.e. instead of the CloudFront distribution http://s111111abcdef8.CloudFront.net/ , the user can specify the custom URL.

9. Provide the logging details. The present guide has selected all the default values for logging. Click on “Create Distribution”.

10. CloudFront will now start to create the distribution. It takes about 5-10 minutes to create a distribution. Initially, when both the distributions (created in steps #5 and #9) are being created, the status will be “In Progress”.

11. Once the distributions have been created, the status will change to “Enable”. Get the domain name of the distribution. The domain name for the download distribution will start with ‘d’ and be in the following format: “d111111abcdef8.CloudFront.net”, while for streaming it will start with‘s’ and be in the following format: “s111111abcdef8.CloudFront.net”.

12. To test the CloudFront distribution, first create an HTML file which uses the download distribution of the video player and the streaming distribution for the media file uploaded to the origin bucket, as explained in step #2.

13. The above mentioned HTML will not work directly from the local machine.. The user can either host it on some web server and request it or upload to the S3 bucket and access it. For the purpose of testing, upload the file to the same bucket where the media player and media files are uploaded. It is not necessary to keep all the files in the same bucket.

14. When the HTML is requested, it can stream the video. The object uploaded in step #2 will be served from the CloudFront edge location and not directly from the S3 origin. The HTML file can be accessed directly from S3 using the URL provided by the S3 bucket.

15. Since a download distribution has been created for this file in step #5, the user can also request the HTML file through the CloudFront distribution.

Keywords: Amazon Web Services, AWS, Amazon AWS Console, AWS S3, Amazon CloudFront, AWS CloudFront, CloudFront, AWS EC2, AWS ELB, JW Player, AWS Distribution Wizard, CDN, Content Delivery Network

How to Create a CloudFront Download Distribution with AWS S3

Newvem Community — Tue, 05 Mar 2022 13:44:35 +0000

AWS CloudFront is a content distribution service offered by AWS to speed up the distribution of static or dynamic content, such as media files, html, js css, etc as well php. CloudFront serves its content through edge locations. As of Dec 2021, AWS had more than 35+ edge locations across the globe. When the user requests for any static content from CloudFront, it will find the nearest edge location to the user and deliver the content from that edge location to reduce the latency.

The present guide demonstrates how to create a download distribution with the AWS S3 service for CloudFront.

CloudFront can serve the content from AWS S3, the user’s own origin server or AWS services, such as EC2, and ELB. In CloudFront, the content is organized into distribution, which specifies the origin or location of the object (AWS S3 bucket or own origin).

1. Create a bucket with AWS S3. Make the bucket publicly accessible with the access policy.

2. Upload the media (image) file to be distributed using CloudFront to the bucket, and make it public.

3. Go to the AWS console through http://aws.amazon.com/console. Click on “CloudFront”.

4. In the CloudFront console, click on “Create Distribution”.

5. In the Create Distribution wizard, select the download distribution. CloudFront also supports the streaming of media files. The present guide explains how to distribute an image file using CloudFront. Click on “Continue”.

6. Provide the origin ID as the bucket name created in step #1. At present accept the default values for “Restrict Bucket Access”.

7. Select the default values of cache behaviors in the same page. In cache behaviors, configure values for:

a. Path pattern is used to apply the cache behavior to specific objects. If default (*) is selected it will forward all requests to the bucket selected in step #6.
b. Viewer Protocol Policy allows the end user to access objects through HTTP and HTTPS.
c. Allow everyone to view the content through “Restrict User Access”.
d. Object Caching allows caching of objects up to 24 hours for the default value. To specify the time, use the customize option.
e. Forward Cookie is for AWS EC2 and the customized origin. It allows customizing whether the user wants to forward cookies to the origin server.
f. The Forward Query string is used to receive different versions of the object based on a query string in the URL.

8. Provide values for the distribution setting as given below:

a. Price Class: Allows the user to select the maximum price to pay for the CloudFront service.
b. CNAMEs allows the user to use URLs for objects instead of the domain name that CloudFront assigns. Thus, instead of the CloudFront distribution http://d111111abcdef8.cloudfront.net/ , the user can specify a custom URL.
c. Default Root Object serves the default root object when the user requests the root URL of the distribution (i.e. user sends request as http://mynvm.com instead of http://mynvm.com/index.html).
d. Cookie Logging is used to allow origins other than AWS S3.
e. Comment is used to describe the distribution.
f. Distribution State, when enabled, allows CloudFront to process requests as soon as the distribution is created.

Click on the “Create Distribution” button after providing values, as explained in steps # 6, 7 and 8.

9. CloudFront will now create the distribution. It takes about 5-10 minutes to create a distribution. Initially, when the distribution is being created, the status will be “In Progress”.

10. Once the distribution has been created, the status will change to “Enable”. The distribution has now been created. Get the domain name of the distribution. The domain name for the download distribution will start with ‘d’ and be in the following format: “d111111abcdef8.cloudfront.net”.

11. To test the CloudFront distribution, first create a HTML file which uses the distribution and requests the image uploaded to the origin bucket, as explained in step #2.

12. When the HTML is requested, it will show the image. The object uploaded in step #2 will be served from the CloudFront edge location and not directly from the S3 origin. The image delivered through CloudFront is marked in the figure given below.

Keywords: Amazon Web Services, AWS, Amazon AWS Console, AWS S3, Amazon CloudFront, AWS CloudFront, CloudFront, AWS EC2, AWS ELB, CDN, Content Delivery Network

Network World Features Newvem as Product of the Week

Cameron Peron — Thu, 28 Feb 2022 14:26:23 +0000

We are proud to announce that Cloud Care has been featured as product of the week on NetworkWorld. Actively tracking AWS cloud health, Cloud Care diagnoses cost, risk, and governance irregularities, triages urgent issues, and tracks cloud vitals such as costs and risks.

Cloud Care is a free solution for all AWS users and used everyday by DevOps, IT Managers, CIOs, CTOs, and Finance departments to get the most out of their AWS resources.

[Newvem analytics tracks your AWS cloud utilization:

Hourly Utilization Pattern Analysis
Reserved Instances Decision Tool
Resource Resizing Opportunities

Get started with Newvem for free or learn more about Newvem's features]

About the Author

Keywords: Amazon Web Services, AWS Cloud, Cloud Usage, Cloud Optimization, Cloud Management, Risks, Assets, AWS Resources, Newvem Business Views, Fault Tolerance, Cloud Costs, Cloud Spend

Newvem on AWS – Customer Success Profile

Ofir Nachmani — Tue, 26 Feb 2022 16:18:28 +0000

You’re sitting at your desk when your manager comes in, or even the CEO. He says “I’ve heard something about that cloud thing. Can it really save me money? Is it secure?”

In this video, Newvem Board Member Mary-Lou Smulders explains how Newvem (previously referred to as ‘that cloud thing’) is building its business using Amazon Web Services.

We do everything on EC2 and it has given us the flexibility and agility we need to maximize our cloud usage. Watch this video to hear what one word Mary-Lou uses to describe the AWS cloud.

[Newvem analytics tracks your AWS cloud utilization:

Hourly Utilization Pattern Analysis
Reserved Instances Decision Tool
Resource Resizing Opportunities

Get started with Newvem for free or learn more about Newvem's features]

About the Author

Ofir Nachmani is Chief Evangelist and Community Leader at Newvem. On his previous adventure, he led ClickSoftware’s Cloud adoption initiative. He also held several positions at Zarathustra SaaS development including ContractorOffice.com product manager and company CEO. In 2009, ClickSoftware acquired the AST group and Zarathustra as part of it. Check out his personal cloud computing blog at http://www.iamondemand.com | Twitter: @iamondeamnd

Keywords: Amazon Web Services, AWS Cloud, Cloud Usage, Cloud Optimization, Cloud Management, Risks, Assets, AWS Resources, Newvem Business Views, Fault Tolerance, Cloud Costs, Cloud Spend

How to Attach an EBS Volume with an AWS EC2 Windows Instance

Newvem Community — Mon, 25 Feb 2022 19:19:54 +0000

The Amazon Elastic Block Store (Amazon EBS) offers persistent storage for the Amazon EC2 instances. Amazon EBS volumes provide a scalable storage service, which persists independently of the instance life. A user can attach an EBS volume to an EC2 instance. It is mandatory that both the volume as well as the instance be in the same availability zone. The user can assign a maximum of 16 EBS volumes to an instance. AWS allows the user to create the EBS volume.

The present guide demonstrates how attach an EBS volume to a Windows instance.

A user has to specify the device name while attaching an EBS volume to an EC2 instance. When a volume is attached to a Windows instance, it is recommended to format the device and mount it as a drive.

1. Go to the AWS console and select the EC2 service. From the EC2 dashboard, click on the “Running Instances” or the “Instance” link.

2. Launch a Windows instance.

3. Go to Volumes and check the currently attached volume information. Create an additional volume in the same zone where the instance is running.

4. Select the volume to be attached. From the “Actions” menu, select “Attach Volume”.

5. AWS will ask for the EC2 instance, where the EBS volume will be attached. The device name should also be provided. Click on “Yes, Attach”.

6. The volume will be attached to the instance and the instance information will be displayed in the volume attachment information.

7. When the user checks the instance information, as explained in step#2, the two devices will be displayed. The newly attached device is shown as xvdf.

8. When the user clicks on the xvdf device, the device information will be displayed.

9. The user is required to format the attached device before using it.

The Amazon Elastic Block Store (Amazon EBS) offers persistent storage for the Amazon EC2 instances. We saw that an EBS volume can be attached to AWS Windows instance for vertical scalability.

The present guide demonstrates how to format an EBS volume attached to a Windows instance.

1. Create an EBS volume and attach it to Windows Instance.

2. Login to the Windows instance. Currently only one disk drive (C Drive) is available in the instance. The new device (volume), which is mounted, is still not available in the instance.

3. Go to the Control Panel -> Administrative Tools. Click on Computer Management.

4. Click “Disk Storage”. If Windows asks to initialize the disk, click on the “OK” button.

5. The new attached volume will be displayed as “Disk1”. It is still unallocated.

6. Right click on “Disk 1” and select “New Simple Volume”.

7. Windows will show the New Simple Volume Wizard. The user can select the default options or the options, such as the drive, and size as per requirement.

8. On completion of the above mentioned steps, the New Simple Volume Wizard will show the summary of all the steps for review. Click on the “Finish” button.

9. On completion of the above mentioned steps, the volume will be formatted.

10. The new volume will be available after formatting as “D Drive”.

11. The new device will now be available in the computer.

Keywords: Amazon Web Services, AWS, Amazon EBS, EBS Volume, AWS EC2, EC2 instances, Cloud Computing, AWS Console, Windows Instance

How to Format an AWS EBS Volume Attached to an EC2 Windows Instance

Newvem Community — Mon, 25 Feb 2022 19:19:13 +0000

The Amazon Elastic Block Store (Amazon EBS) offers persistent storage for the Amazon EC2 instances. We saw that an EBS volume can be attached to AWS Windows instance for vertical scalability.

The present guide demonstrates how to format an EBS volume attached to a Windows instance.

1. Create an EBS volume and attach it to Windows Instance.

2. Login to the Windows instance. Currently only one disk drive (C Drive) is available in the instance. The new device (volume), which is mounted, is still not available in the instance.

3. Go to the Control Panel -> Administrative Tools. Click on Computer Management.

4. Click “Disk Storage”. If Windows asks to initialize the disk, click on the “OK” button.

5. The new attached volume will be displayed as “Disk1”. It is still unallocated.

6. Right click on “Disk 1” and select “New Simple Volume”.

7. Windows will show the New Simple Volume Wizard. The user can select the default options or the options, such as the drive, and size as per requirement.

8. On completion of the above mentioned steps, the New Simple Volume Wizard will show the summary of all the steps for review. Click on the “Finish” button.

9. On completion of the above mentioned steps, the volume will be formatted.

10. The new volume will be available after formatting as “D Drive”.

11. The new device will now be available in the computer.

Keywords: Amazon Web Services, AWS, Amazon EBS, EBS Volume, AWS EC2, EC2 instances, Cloud Computing, AWS Console, Windows Instance

How to Modify the Instance Initiated Shutdown Behavior

Newvem Community — Mon, 25 Feb 2022 09:30:56 +0000

AWS has two types of AMIs: Instance Store backed and EBS backed. The EBS backed instance can be started or stopped using AWS APIs or the console. The user can configure the application by connecting to the instance. In certain cases, the user can shutdown the instance from the OS directly. The present guide demonstrates how to change the instance initiated shutdown behavior. This is applicable to only the EBS backed instance and when the instance is shut down internally.

For example, from Windows the user can shut down through the Start Menu (For OS Win 7 and before) or through shutdown from Linux. When the user shuts down the instance internally from the OS, by default the instance gets stopped. AWS provides a functionality, whereby the user can change the default shut down behavior such that when the instance is shut down internally, the instance gets terminated instead.

1. Go to the AWS console and select the EC2 service. From the EC2 dashboard, click on the “Running Instances” or “Instances” link.

2. Select the instance for which the shutdown behavior is required to be changed. Click on the “Actions” menu.

3. Select “Change Shutdown Behavior” from the “Actions” menu.

4. AWS will show the current shutdown behavior and ask the user to change if required. Change the shutdown behavior to “Terminate”. Select the “Yes, Change” button.

5. The shutdown behavior will be changed to terminate.

6. Launch an AWS instance. Login to the instance.

7. If it is a Linux instance, run the command “shutdown –h now”. In Windows, shutdown the machine using the “Start Menu” (Win 2007 Serves). The instance will start shutting down.

8. AWS will show the instance status as shutting down.

9. When the instance shuts down, if the shut down behavior is not set, AWS will stop the instance. Here, the user has set the shutdown behavior in step#4. Thus, AWS will terminate the instance.

10. To run the above mentioned steps through the command line interface, first setup AWS EC2 CLI to launch an instance with the command line option, as explained here.

11. Run the command:

 ec2-describe-instance-attribute  --instance-initiated-shutdown-behavior.

Run the command:

 ec2-modify-instance-attribute  --instance-initiated-shutdown-behavior terminate

to change the shutdown behavior to terminate.

12. The actual output of the above mentioned commands is shown below:

Keywords: Amazon web services, Amazon AWS console, Amazon AWS instances, EC2 Service, Amazon cloud computing, EC2 EBS, Instance Store Backed, EBS Backed Instance, AMI