You may wish to use the [[#CFTemplate|CloudFormation template]] and launch your instance with some smart [[#UserDataExamples|UserData scripts]]. For some releases you are free to choose the AWS Marketplace AMI, or the AMI that exists in the Debian AMI Account (account number 379101102735). All AMIs shared from the Debian AWS Account and their corresponding EBS snapshots are marked as public so can be inspected by any other AWS user.

{{{#!wiki note'''SSH username'''

In line with the security of most Linux distributions on ''Amazon Web Services'', remote ''root'' SSH is disabled (as is password authentication). You will need to connect to instances from this AMI as the user '''admin''' using your SSH key, and then '''sudo -i''' to gain root access.}}}

Please note that a Marketplace image volume cannot be attached to another running instance (For example, to repair a broken /etc/fstab, or /etc/network/interfaces). This is a limitation of all Marketplace images, as described here: [[http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-AttachVolume.html|Official AWS documentation]]

You may wish to use a [[#CFTemplate|CloudFormation template]] and add a [[#UserDataExamples|UserData script]]. For some releases are duplicated into ''Amazon Marketplace'' but the same images are shared directly as "Community Shared AMIs" (account number 379101102735, but with different AMI IDs to the Marketplace). All AMIs shared from the Debian AWS Account and their corresponding EBS snapshots are marked as public so can be inspected by any AWS user.

{{{#!wiki note'''SSH username'''

Remote ''root'' SSH is disabled in all images, as is password authentication). You will need to connect to instances from these AMIs as the user '''admin''' using your SSH key, and then '''sudo -i''' to gain root access.}}}

Please note that an ''Amazon Marketplace'' image volume cannot be attached to another running instance (For example, to repair a broken /etc/fstab, or /etc/network/interfaces). This is a limitation of all Marketplace images, as described here: [[http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-AttachVolume.html|Official AWS documentation]]

As is standard with Debian, a simple '''apt-get update && apt-get dist-upgrade''' should bring all packages up to date. There is no need to reinstall, but any CloudFormation templates and AutoScale Launch Configurations should be tested with and then updated to use the current AMI. It is recommended not to use older point releases.

As is standard with Debian, a simple '''apt-get update && apt-get dist-upgrade''' should bring all packages up to date. There is no need to reinstall, but any !CloudFormation templates and !AutoScale Launch Configurations should be tested with and then updated to use the current AMI. It is recommended not to use older point releases.

As of the 7.3 release, the official Debian !AMIs now support cloud-init. This means you havemuch more flexibility (and power) in what you can putin your !UserData to get your instance to configure. For example, a simple shell script that starts with {{{#!/bin/sh}}} will be executed as previously - so you can chose to enable auto update with the following !UserData scripts:

Debian !AMIs use cloud-init. This gives you a choice when crafting your !UserData to configure your instance. Simple shell scripts continue to be supported by starting with {{{#!/bin/sh}}},such as:

Some feature bugs may persist in Cloud-init in Debian 7.3 AMIs; no functionality has been lost, but it appears not all cloud-init directives can be used. Eg: packages, ssh-import-id, apt_update, apt-upgrade.

Debian Wheezy (7.x) on AWS EC2

7.8.aws.1 (28 January 2015)

This release addresses CVE 2015-0235 also known as the "ghost" issue with libc6; it contains the updated libc6 in the base image.

Region

hvm x86_64 ebs

paravirtual i386 ebs

paravirtual x86_64 ebs

paravirtual x86_64 instance-store

ap-northeast-1

ami-b25d44b3

ami-c05e47c1

ami-e05c45e1

ami-745c4575

ap-southeast-1

ami-aeb49ffc

ami-c08ba092

ami-008ba052

ami-6a8ba038

ap-southeast-2

ami-6b770351

ami-f17703cb

ami-b777038d

ami-4f770375

eu-central-1

ami-98043785

ami-c80437d5

ami-b60437ab

ami-8a043797

eu-west-1

ami-61e56916

ami-1be06c6c

ami-e7e66a90

ami-c9e569be

sa-east-1

ami-3d8b3720

ami-6b8b3776

ami-558b3748

ami-2f8b3732

us-east-1

ami-e0efab88

ami-e6eeaa8e

ami-baeda9d2

ami-74efab1c

us-west-1

ami-b4869ff1

ami-a8b9a0ed

ami-c0b9a085

ami-70b9a035

us-west-2

ami-431a4273

ami-051b4335

ami-f91a42c9

ami-a31a4293

us-gov-west-1

ami-d13455f2

ami-d53455f6

ami-d73455f4

-

cn-north-1

ami-48029071

-

ami-5c029065

-

A GPG signed email of this list is in the Debian-Cloud mailing list archive for your security.

You may wish to use a CloudFormation template and add a UserData script. For some releases are duplicated into Amazon Marketplace but the same images are shared directly as "Community Shared AMIs" (account number 379101102735, but with different AMI IDs to the Marketplace). All AMIs shared from the Debian AWS Account and their corresponding EBS snapshots are marked as public so can be inspected by any AWS user.

SSH username

Remote root SSH is disabled in all images, as is password authentication). You will need to connect to instances from these AMIs as the user admin using your SSH key, and then sudo -i to gain root access.

Please note that an Amazon Marketplace image volume cannot be attached to another running instance (For example, to repair a broken /etc/fstab, or /etc/network/interfaces). This is a limitation of all Marketplace images, as described here: Official AWS documentation

Upgrading from previous 6.x.y releases

As is standard with Debian, a simple apt-get update && apt-get dist-upgrade should bring all packages up to date. There is no need to reinstall, but any CloudFormation templates and AutoScale Launch Configurations should be tested with and then updated to use the current AMI. It is recommended not to use older point releases.