ami

What the title says. Within the master AWS account, I have several personal accounts, i.e. AWS Identity and Access Management (IAM) users. I would like to assign certain IAM users to groups and prevent them from terminating certain Amazon EC2 instances , de-registering certain Amazon Machine Images (AMIs) , etc. I don't mind if they're playing with their own stuff, but I don't want them to touch my stuff. Is that possible? Update AWS has just announced Resource-Level Permissions for Amazon EC2 and Amazon RDS to address this long standing shortcoming of IAM support within EC2 and RDS (in

I have created my own EBS AMI, shared it with another AWS account, launched NEW instance based on this image with NEW key-pair and now when I am trying to connect to this new instance I am getting error: "Server Refused our key". This is what I did (step by step): Configured new CentOS 6.3 server in my personal account (with my personal key-pair) Created EBS AMI image of that server Shared this image with my client's account Launched new instance in my clients account based on this shared image + new key-pair New launched instance doesnt want to take new key-pair. After some testing I figure

I want to create an EC2 cloudformation stack which basically can be described in the following steps: 1.- Launch instance 2.- Provision the instance 3.- Stop the instance and create an AMI image out of it 4.- Create an autoscaling group with the created AMI image as source to launch new instances. Basically I can do 1 and 2 in one cloudformation template and 4 in a second template. What I don't seem able to do is to create an AMI image from an instance inside a cloudformation template, which basically generates the problem of having to manually remove the AMI if I want to remove the stack.

Question: How should I use the new AWS EC2 classes (r3, i2) with my existing AMI without recreating the whole system setup? The new EC2 classes support only HVM based virtualization but I have only PVM AMI images. divyenduz Answer: Start an Ubuntu HVM linux, any version, new Start an Ubuntu / with my existing AMI / PVM linux, and install grub packages on them: apt-get install grub-pc grub-pc-bin grub-legacy-ec2 grub-gfxpayload-lists Stop PVM linux Detach root (/dev/sda1) partition at PVM linux Attach PVM linux root partition to running HVM linux somewhere, e.g.: /dev/sdf On HVM linux: mkdir -p

Any easy way to move and custom AMI image between regions? (tokyo -> singapore) I know you can mess up with API and S3 to get it done, but there there any easier way to do it? As of December, 2012, Amazon now supports migrating an AMI to another region through the UI tool (Amazon Management Console). See their documentation here So, how I've done it is.. From the AMI find out the Snapshot-ID and how it is attached (e.g. /dev/sda1) Select the Snapshot, click "Copy", set Destination region and make the copy (takes a while!) Select the new Snapshot, click " Create Image " Architecture : (choose

Defining userdata for instances in AWS seems really useful for doing all kinds of bootstrap-type actions. Unfortunately, I have to use a custom CentOS AMI that didn't originate from one of the provided AMIs for PCI reasons, so cloud-init is not already installed and configured. I only really want it to set a hostname and run a small bash script. How do I get it working? whereswalden cloud-init is a very powerful, but very undocumented tool. Even once it's installed, there are lot of modules active by default that overwrite things you may have already defined on your AMI. Here are instructions