Hot answers tagged amazon-ami
An AMI is, as you note, a machine image. It's a total snapshot of a system stored as an image that can be launched as an instance. We'll get back to AMI's in a second. Lets look at EBS. Your other two items are sub-items of this. EBS is a virtual block device. You can think of it as a hard drive, although it's really a bunch of software magic to link into ...
Since this question was written, Amazon completely revamped for Amazon Linux AMI 2011.09, with all the bootstrapping for CloudFormation as well as Amazon tools. Also, it includes Nginx and PHP-FPM in the yum repos if you're looking for fast and light. Keep up with the latest releases here: http://aws.amazon.com/amazon-linux-ami/latest-release-notes/ Also ...
When you attach an EBS volume, you specify the device to attach it as. Under linux, these devices are /dev/xvd* - and are symlinked to /dev/sd* In the AWS console, you can see your EBS volumes, what instances they are attached to, and the device each volume is attached as: You can achieve the same thing from the CLI tools. Set the necessary environment ...
Worked for me: yum remove php httpd php-cli php-xml php-common httpd-tools yum install php55 php55-mysql php55-pdo
I was in a similar situation; fully managed dedicated server, LAMP, CentOS. Then we decided to move to EC2. Also, I had very little systems or linux administration experience. I have almost zero experience with Ubuntu, so I really cannot speak to which is the so-called better OS. I tried a bunch of pre-built AMI's with minimal OS installs from ...
Best practices: Whenever you build an AMI (or even set up an instance) always document the exact steps you took to install and configure the software and what data you put on it and where. This has many benefits including making it easy to rebuild the same AMI for a different architecture. Even better, I recommend scripting most or all of the install, ...
I ran into the same problem when trying to duplicate a machine. The problem turned out to be the kernel. Both when creating the AMI and the instance I selected default for the kernel image. To resolve the problem, I recreated the AMI using the same kernel image as the original instance.
I'm not sure about shared AMIs, but many things in EC2 are segmented by region and you have to select the correct region to see them. You can select the region in the upper right-hand corner of the screen.
You list "1690 GB of instance storage". It isn't clear if you were just quoting the specs of your instance type or if you have actually formatted and are using all that storage. It isn't clear from the question exactly what storage you want to increase. Here are some thoughts on different situations: It is not possible to increase instance-store beyond ...
The approach I take to decreasing an EBS root volume is as follows: Stop (not terminate) the target instance, and detach the root EBS volume. Alternatively, you can snapshot the root volume (or use an existing snapshot) and create a new EBS volume from that. (e.g. /dev/xvda1) Note: the volume you use from the step above will be altered - so you may want to ...
The only fastest way is that which you have mentioned already, that make a small ami and host a static maintenance page on it, by attaching elastic IP to it. There is no hard and fast rule that which AMI should be used in this scenario. Any micro instance of Debian/RHEL/Ubuntu would work fine.
No, there is no automated way. You will have to create a new AMI starting with the Ubuntu-plain one. It's possible to convert an Unbuntu installation but it's really messy. It's best you make a fresh AMI.
You can use the ec2-undbundle tool to download any AMI you control. As you can make an AMI of an instance, this should be no trouble.
Actually, your best bet is probably the Amazon Linux AMI: http://aws.amazon.com/amazon-linux-ami/ It's CentOS/RHEL under the hood, so you can use all the CentOS RPMs and such, but you get Amazon's tweaks and improvements so it runs even better in EC2.
Make sure the time zone is also changed in /etc/sysconfig/clock by setting ZONE="America/New_York"
It's actually an error page, and gets served because index.html is missing. You should find it somewhere in the vicinity of /var/www/error/noindex.html
It's not the TTYs you would disable; it is the gettys (you can also modify udev rules to not create device files for the ttys, but they are implemented in the kernel). If you log in only via SSH and do not log in through any of the console ttys or a serial tty ever, by all means remove the inittab rules that run a getty on them. However, I would personally ...
imagecreatefromjpeg is in php-gd mb_strlen is in php-mbstring So install them via yum install php-gd php-mbstring
I believe your only option is to create a new AMI from one of your configured instances. Then you will have to spin up new instances based on that AMI and remove the ones on the old AMI.
The official amazon images come quite minimal with only a local sendmail daemon, ntpd, dhcp client, crond, atd, rsyslog and a few other services running. Based on this install and the default security groups, the Amazon Linux AMI is already as minimal as it can be.
Did you allow ICMP and other traffic in security group settings? You should check the security group settings. It looks like you are using a default security group as seen on the 2nd row of 2nd column of the table on your screenshot. You should click "view rules" and adjust the rules there.
Take a step back. The PCI scanner is blindly relying on version numbers and isn't taking into account that the vendor (which is eventually Red Hat) backports patches. Find out the exact vulnerability (get the CVE) and then use rpm -q --changelog httpd (or go to http://cve.mitre.org/cve/cve.html and https://access.redhat.com/security/updates/ ) to see if the ...
Maintainers of third party repositories should name their packages in a way that doesn't interfere with the main repository, otherwise conflicts like this will happen. YUM priorities You can use Yum Priorities configure each repo to use a certain priority by assigning priority=N to the repositories listed in the .repo file. Some Yum developers have ...
Although Ubuntu does better on these benchmarks, the tests themselves contribute towards Ubuntu winning, and the differences don’t seem to be big anyway. I recently chose Amazon Linux largely because of automatic updates, and also because of the Ubuntu AMI bug reported by Steven and Ethan in the Quora version of this question.
Can i create a S3-backed / instance-store AMI out of an EBS based instance? Yes, you can create an Instance-store AMI out of an EBS based instance. Install ec2-ami-tools in the instance Upload your x509 certificates to the instance Use ec2-bundle-vol and ec2-upload-bundle commands NOTE: You need your account ID, Access Key and Secret Key to ...
If you still have access to the instance, I believe the simplest way would be using "dd" to copy it off to a raw file (possibly just directly piping over SSH to the destination system like in ssh your.ec2-syst.em 'dd if=/dev/sdh bs=1M | gzip' | gunzip | dd of=/tmp/ec2-image.raw) and then using something like qemu-img to convert the raw image to a VMDK file.
By default, when creating an AMI image of an EBS-boot instance, the instance will be shutdown. The benefit of shutting down is that the filesystem is ensured to be in a consistent state (no partial file writes). Using the Amazon AWS Management Console, you're forced to stop the instance when creating the AMI image. However, when using the API or ...
From what I've found in researching bits and pieces, it's not easy to do. To get the image, you can take a snapshot, and mount it to a running instance then just copy down the contents to a local raw file with something like dd over ssh. Then disconnect the volume from the instance, verify you have the image locally stored, and delete the EBS block. That ...
Go ahead and do sudo yum remove php-common, it will be installed again when you do sudo yum install php55. Same goes for any other conflicts.
It's broke, fix it. chkconfig nginx on In your current configuration, nginx is never started automatically. Note that the symlinks that start with K indicate that the service will be stopped (killed) in that runlevel. Symlinks that start with S indicate that the service will be started.
Only top voted, non community-wiki answers of a minimum length are eligible