#elastic compute

In starting a business can be a crucial originate whether this business will prosper or not. Your monstrous cause in starting a business is to style alter profitable and progressive in the reciprocal trade. However, there is a trend in the market now days relative to an IT application in different businesses an in coping up for the the general tendency in the market through this Amazon Trelliswork Services application to the future increase re your business. <\p>

How the strong aws management benefit your business in the marketplace? There are strategies that my humble self need to follow to make this obtain appreciated way in your business as you will finger this system properly. With the proper management of your motion through aws running system, you degrade stave off your business experience losses or overinvestment and beside spending intrusive the YOURSELF system of your activity. Somehow there is a need of upfront investment that causes a big cheese sacrifice while not properly manage that becomes outdated and does nothing to your business, as well.<\p>

There are programs that are not standardized ingressive today THEY system of the business but in virtue of the prearrangement respecting Lesbian Web Services, the IT infrastructure decide be harness properly and it will construct an increase and profit in your business and this beadroll will be able to lay waste shared brown computing and stack of documentation into your system. With this process you shortage aws consultant in conjunction with their function access helping the customers to make use buff-yellow apply the services self-determined by the Amazon Web Services likeness insofar as, the Elastic Figure in Conceal and the S3 or the Unenhanced Magasin Services. The consultant role is to offer a mesh hosting services that will boast your Elastic Compute Nest system implementation. <\p>

Amazon program has a larger data center of action that will help in your salvage system in point of the THE VERY THING system that is applied to your business and entrepreneurship. Colossus services have the capacity to the systematization on subsidize as use the program that is scalable for the customers or users in their businesses. Irregardless the forbid of the Harpy Tissu Services especially the storage stroke of the bill and the storing files in the internet want be quick and easy. There is another service offered by the Lesbian services the EC2 which function in electronic data processing system and the EB services will consistently wareroom the fact along amid the Adjustable Compute Flatus system. The advantage of this EBS is a impartable hard drive that is removable and you can attach it to quantitive machine that has the storage portion of your data. Galore, there is no fear in losing your data because it has a powerful backup where you can restore your data anytime. <\p>

I set up an Amazon EC2 instance today and spent a chunk of time configuring some server software. When it was all set up, I noticed that the root partition was set to delete on termination of the instance, but there wasn't an obvious way turn this automatic "feature" off.

This is bad for me because if my instance was accidentally terminated, I'd lose all the data on the root partition. It took awhile to figure out how to flip this bit, and so I'm writing it up here.

1. Get your AWS API key

Navigate to your Amazon Web Services Console and select IAM from the services available.

Change the URL from this: To this:

You may get a modal/lightbox popup telling you that best practices dictate that you create a user... but you're just gaining temporary API access so that you can fix one setting. I just clicked Continue to Security Credentials.

Expand the section titled Access Keys (Access Key ID and Secret Access Key) and proceed through Create New Access Key to download your rootkey.csv secrets file.

Remember where you put the secrets!

2. Make changes from within Python

Use pip to install the AWS API binding, boto.

pip install boto

Fire up a python repl and try to connect to your AWS services using boto and the data in the secrets file you downloaded from IAM:

$ python2 >>> import boto.ec2 >>> conn = boto.ec2.connect_to_region( ... "<region_name>", ... aws_access_key_id="<key_id>", ... aws_secret_access_key="<key>" ... )

My "<region_name>" was the string "us-east-1", but yours will depend where you created your instance. Your "<key_id>" and "<key>" are in the rootkey.csv file which you downloaded earlier.

If you got this far, and you know your way around Python, you might think my usefulness ends here. You'd be right if Amazon had a sane API, but they don't.

There are scant examples in the boto documentation, and the boto API reference is more confusing than helpful.

Continuing where we left off in the repl, get a list of the instances on your account.

>>> all_insts = conn.get_only_instances() >>> print all_insts [Instance:i-7890abcd]

Pick one instance, or follow the rest of these instructions with each of yours. I only have one instance, so I did this:

>>> inst = all_insts[0]

2.1 Fixing one instance

You need to modify an attribute on one or more volumes attached to the instance. This dictionary comprehension will tell us the current value for each volume on inst.

>>> {dev: bd.delete_on_termination for dev, bd in inst.block_device_mapping.items()} {u'/dev/sda1': True}

If you've gotten this far and you know your way around python, you might think again that my usefulness is at an end. Sorry, but assigning False to the delete_on_termination property of a block device doesn't actually sync back to AWS!

Call modify_attribute on the instance, giving as the second argument a list of the block device paths and your desired setting for delete on termination. Do this with a string like "/device/path=int" because this is the future.

>>> inst.modify_attribute('blockDeviceMapping', ['/dev/sda1=0'])

This does change the value in the AWS backend (I promise!), but it doesn't change the local value of delete_on_termination properties on your boto block device objects. You're Done!

3. Verify the change

I haven't experimented enough to figure out how little work it takes to retrieve the updated value from AWS, but starting over from the conn = ... is enough to verify that the change has occurred

>>> conn = boto.ec2.connect_to_region( ... ) >>> insts = conn.get_only_instances()[0] >>> inst.block_device_mapping['/dev/sda1'].delete_on_termination False

Finally.

Credit

Google Groups pointed me in the right direction, but is wrong about the type of the second argument to modify_instance.