Please upgrade to Amazon Linux AMI 2015.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 2015.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 November 2, 2015

  • We've updated the base AMI to include all bugfix and security updates that have been made available in our repositories since the 2015.09 release.
  • This point release includes the 4.1.10 kernel.

Having spent the past year tracking the 3.14 kernel series, for this release we have moved the kernel to version 4.1.7, which is the most recent long-term stable release kernel. Of particular interest to many customers is the support for OverlayFS in the 4.x kernel series.

We introduced a Java JDBC driver for Amazon Aurora and MariaDB databases. This driver can connect to multiple Aurora nodes, allowing faster fail-over compared to DNS-based fail-over. The package is available via sudo yum install mariadb-connector-java.

Based on numerous customer requests and in order to support joining Amazon Linux AMI instances to an AWS Directory Service directory, we have added Samba 4.1 to the Amazon Linux AMI repositories, available via sudo yum install samba.

Numerous customers have asked for PostgreSQL 9.4 and it is now available in our Amazon Linux AMI repositories as a separate package from PostgreSQL 9.2 and 9.3. PostgreSQL 9.4 is available via sudo yum install postgresql94 and the 2015.09 Amazon Linux AMI repositories include PostgreSQL 9.4.4.

A frequent customer request has been MySQL 5.6, and we are pleased to offer it in the 2015.09 repositories as a separate package from MySQL 5.1 and 5.5. MySQL 5.6 is available via sudo yum install mysql56 and the 2015.09 Amazon Linux AMI repositories include MySQL 5.6.26.

We introduced support for Docker and Go in our 2014.03 AMI, and we continue to follow upstream developments in each. The lead-up to the 2015.09 release included an update to Go 1.4 and to Docker 1.7.1.

We have added the AWS CloudHSM CLI tools to our repositories, installable via sudo yum install aws-cloudhsm-cli. The AWS CloudHSM service uses dedicated Hardware Security Module (HSM) appliances, allowing customers the ability to control the encryption keys and cryptographic operations performed by the HSM.

We already provide Python 2.6, 2.7 (default), and 3.4 in the Amazon Linux AMI, but several customers have also asked for the PyPy implementation of Python. We're pleased to include PyPy 2.4 in our preview repository. PyPy 2.4 is compatible with Python 2.7.8 and is installable via sudo yum --enablerepo=amzn-preview install pypy.

We already provide OpenLDAP 2.4.23 in the main Amazon Linux AMI repositories, but customers have asked for a newer version of OpenLDAP. We've included OpenLDAP 2.4.40 in our preview repository, and we will work to integrate it into our main repository in the future. It is installable via sudo yum --enablerepo=amzn-preview install openldap.

In our 2015.03 release notes we added an initial preview of the Rust programming language. Upstream development has continued on this language, and we have updated from Rust 1.0 to Rust 1.2 for the 2015.09 release. You can install the Rust compiler by running sudo yum --enablerepo=amzn-preview install rust.

Update 2015-09-28: Rust 1.3 is now available in our "Preview" repository.

The following is only applicable to the GPU AMIs that we built specifically for the CG1 instance family.

In our 2014.09 release notes we announced that we would no longer produce GPU AMIs, recommending migration to the Graphics AMI and the G2 instance type. Our 2015.03 release notes reinforced this message, as we did not provide a GPU AMI for that release though we did still provide package updates in the GPU repository.

A full year later, we are now no longer producing any GPU package repositories. This means that existing GPU instances using the "latest" releasever will no longer receive updates to NVIDIA or CUDA-related packages and may see errors regarding the GPU repo when using yum. If you update your kernel using the 2015.09 release or later and reboot, you will no longer be able to use the nvidia module.

Our recommendation for all Amazon Linux AMI GPU customers is to migrate to the Graphics AMI. The Graphics AMI has newer NVIDIA and CUDA software available and runs on the more powerful G2 instance type. We believe you'll find it more efficient and less expensive than the CG1 instance type.

In this release, system call auditing has been disabled by default to improve overall system performance. This change is only applied automatically to new instances created from 2015.09 AMIs. See below for instructions on changing existing instances.

If you need system call auditing, please find the following line in /etc/audit/audit.rules and remove it or comment it out, then restart the audit daemon.

 -a never,task

Example (as root):

# auditctl -l
LIST_RULES: task,never
# sed -i.bak -e '/^-a never,task$/ s/^/#/' /etc/audit/audit.rules
# /etc/init.d/auditd restart
# auditctl -l
No rules

If you want to get the same performance improvement on existing instances, please add the line above to /etc/audit/audit.rules and restart the daemon. If you have not made any changes to audit rule files, you can simply move or copy the new default rules file to /etc/audit/audit.rules

Example (as root):

# auditctl -l
No rules
# cp -p /etc/audit/rules.d/audit.rules.default /etc/audit/audit.rules
cp: overwrite ‘/etc/audit/audit.rules’? y
# /etc/init.d/auditd restart
# auditctl -l
LIST_RULES: task,never

Many of our packages have been re-synced to newer upstream versions.  Some of the more popular packages in 2015.09 are:


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 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!  :-)