Please upgrade to Amazon Linux AMI 2014.09 from earlier versions!
While older versions of the AMI and its packages will continue to be available for launch in Amazon EC2 even as new Amazon Linux AMI versions are released, we encourage users to migrate to the latest version of the AMI and to keep their systems updated. In some cases, customers seeking support for an older version of the Amazon Linux AMI through AWS Support may be asked to move to newer versions as part of the support process.
To upgrade to Amazon Linux AMI 2014.09 from 2011.09 or later, run sudo yum update. When the upgrade is complete, reboot your instance.
Remember that the Amazon Linux AMI repository structure is configured to deliver a continuous flow of updates that allow you to roll from one version of the Amazon Linux AMI to the next. Please consult our lock-on-launch FAQ for a discussion of how you can lock an instance (either a new launch or already running) to a particular version of the Amazon Linux AMI repositories.
Released on January 29, 2015
- We've updated the base AMI to include all bugfix and security updates that have been pushed to our repositories since the 2014.09.1 release. This includes the "ghost" patches.
Released on October 14, 2014
- We've updated the base AMI to include all bugfix and security updates that have been pushed to our repositories since the initial 2014.09 release. This includes the "shellshock" patches.
We introduced GP2-by-default AMIs as part of our 2014.03.2 release, and they are included in our 2014.09 release.
Having spent the past release tracking the 3.10 kernel series, for this release we have moved the kernel to version 3.14.19, which is the most recent long-term stable release kernel.
Additionally, instances running the HVM AMIs will now restart 30 seconds after a kernel panic, instead of hanging indefinitely.
Customers who depend on the previous HVM AMI behavior to remove faulty hosts from their fleet can adjust the kernel.panic setting by creating a new file -- /etc/sysctl.d/99-override.conf with kernel.panic=0 as the contents.
PV AMIs have always restarted on kernel panic.
While Ruby 2.0 remains our default Ruby interpreter, we have added ruby21 packages to this Amazon Linux AMI release.
Also, we have updated all of our versions of Ruby to newer upstream patch levels:
While Java 7 is still the default on the AMI, OpenJDK 1.8 is included in the repositories with the java-1.8.0-openjdk package name.
Based on customer requests, we have added tomcat8 to the Amazon Linux AMI repositories.
Also, we have updated all of our versions of Tomcat to the most recent upstream releases:
Numerous customers have asked for PostgreSQL 9.3, and it is now available in our Amazon Linux AMI repositories as a separate package from PostgreSQL 9.2.
PostgreSQL 9.3 is specifically named postgresql93 and the 2014.09 Amazon Linux AMI includes PostgreSQL 9.3.5.
Running yum install postgresql9 or yum install postgresql92 will still install PostgreSQL 9.2.
After a truly spectacular number of customer requests, we introduced Docker in the 2014.03 Amazon Linux AMI. With this release, we continue to track upstream development closely.
Also based on customer requests, this release of the Amazon Linux AMI comes with Nginx 1.6.1.
With the 2014.09 Amazon Linux AMI release, we've moved from Git 1.8 to Git 2.1. Users upgrading from older releases will move directly from the older git to the newer.
We have updated all of our PHP packages to newer upstream versions:
In addition to the features above, here are some other new packages added to our repositories, based on customer requests:
Lots and lots of perl modules
Many of our packages have been re-synced to their latest upstream version.
Some of the more popular package updates are:
We have included updated versions of many AWS command line tools. If there is an additional AWS tool that you would like, please call it out!
We have discontinued support for Python 2.4, GCC 4.6, and GCC 4.7 in this Amazon Linux AMI release.
This compatibility table shows which Amazon Linux AMI flavors are recommended for each EC2 instance type.
The Amazon Linux AMI FAQs is updated with both general and technical topics.
We are planning on deprecating several of our AMI flavors with the 2015.03 release, as follows:
- We will no longer produce new 32-bit Amazon Linux AMIs.
- We will no longer produce new "gpu" AMIs for the CG1 instance type. We recommend that customers migrate to the G2 instance type and the "graphics" AMI.
Please let us know if you have feedback or concerns about any of these plans.
We use the Amazon EC2 Discussion Forum for bug reports, feature requests, and package requests. These forums are monitored by AWS Developer Support as well as the Amazon Linux AMI engineering team.
We are actively hiring Linux Systems Engineer, Linux Software Development Engineer, and Linux Kernel Engineer positions! :-)