Differences between revisions 17 and 18
Revision 17 as of 2017-12-31 20:25:37
Size: 3640
Comment:
Revision 18 as of 2018-01-06 18:30:45
Size: 3858
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 * '''2018-01-06''' Debian 9.3 AMIs updated to include kernel updates for [[https://www.debian.org/security/2018/dsa-4078|DSA 4078]], addressing the [[https://nvd.nist.gov/vuln/detail/CVE-2017-5754|Meltdown attack]].
Line 34: Line 35:
AMI name is "`debian-stretch-hvm-x86_64-gp2-2017-12-24-71024`" and it is owned by AWS account ID `379101102735`. AMI name is "`debian-stretch-hvm-x86_64-gp2-2018-01-06-16218`" and it is owned by AWS account ID `379101102735`.
Line 40: Line 41:
|| `ap-northeast-1` || `ami-f0188d96` ||
|| `ap-northeast-2` || `ami-6a9d3c04` ||
|| `ap-south-1` || `ami-8892d8e7` ||
|| `ap-southeast-1` || `ami-c09af3bc` ||
|| `ap-southeast-2` || `ami-b6d525d4` ||
|| `ca-central-1` || `ami-1545ff71` ||
|| `eu-central-1` || `ami-e49e098b` ||
|| `eu-west-1` || `ami-d133bfa8` ||
|| `eu-west-2` || `ami-babea7de` ||
|| `eu-west-3` || `ami-d0398ead` ||
|| `sa-east-1` || `ami-7027671c` ||
|| `us-east-1` || `ami-7c6b2d06` ||
|| `us-east-2` || `ami-95b79ff0` ||
|| `us-west-1` || `ami-aa1610ca` ||
|| `us-west-2` || `ami-f1e74889` ||
|| `ap-northeast-1` || `ami-a3ed72c5` ||
|| `ap-northeast-2` || `ami-01d5756f` ||
|| `ap-south-1` || `ami-9e7b2ff1` ||
|| `ap-southeast-1` || `ami-d71869ab` ||
|| `ap-southeast-2` || `ami-532cde31` ||
|| `ca-central-1` || `ami-d5e164b1` ||
|| `eu-central-1` || `ami-b58f1cda` ||
|| `eu-west-1` || `ami-867ceaff` ||
|| `eu-west-2` || `ami-e1e8f085` ||
|| `eu-west-3` || `ami-9a19aee7` ||
|| `sa-east-1` || `ami-d0d596bc` ||
|| `us-east-1` || `ami-628ad918` ||
|| `us-east-2` || `ami-2cf4df49` ||
|| `us-west-1` || `ami-6d03030d` ||
|| `us-west-2` || `ami-a0f247d8` ||

Debian Stretch on Amazon EC2

SSH username

SSH to Debian instances as user admin using your SSH key, and then sudo -i to gain root access.

Status

  • 2018-01-06 Debian 9.3 AMIs updated to include kernel updates for DSA 4078, addressing the Meltdown attack.

  • 2017-12-24 Debian 9.3 AMIs updated to include DSA 4071 and DSA 4073 updates. These are also the first AMIs published to the new eu-west-3 (Paris) region.

  • 2017-12-17 Debian 9.3 AMIs available. See the release announcement for details.

  • 2017-10-08 Debian 9.2 AMIs available. See the release announcement for details.

  • 2017-08-31 Debian 9.1 AMIs have been refreshed with package updates available as of 2017-08-31. AMI details are available below.

  • 2017-07-22 Debian 9.1 ("stretch r1") AMIs available. Details about updated packages can be found in the release announcement.

  • 2017-06-21 Stretch release AMIs available. Notable changes include passing 'net.ifnames=0' to address Bug 863385 and the installation of unattended-upgrades. Details below.

  • 2017-04-20 The second pre-release round of EC2 AMIs was announced. See AMI details below, or the blog announcement

  • 2017-01-28 The first pre-release round of EC2 AMIs was announced in January, 2017. Details on Noah's blog

Image notes

  • HVM images only - current generation EC2 instances all support HVM virtualisation.

  • 64-bit images only - current generation EC2 instances all support 64 bit; if you require 32 bit, please look at Multiarch

  • SR-IOV networking - Enhanced Networking (ENI)

  • ENA networking - Elastic Network Adapter

  • Multiple ENI support - DHCP client is configured to support the number of network interfaces the instance supports (up to 8), hot plugged with udev

  • Multiple sub-interfaces - DHCP client is configured to support multiple IP addresses per interface

  • AWS CLI is installed by default

  • Python-boto is installed by default

  • apt-transport-https is installed; you can change your sources.list to https://cloudfront.debian.net (or other https site) if you wish!

Stretch

AMI name is "debian-stretch-hvm-x86_64-gp2-2018-01-06-16218" and it is owned by AWS account ID 379101102735.

The update to the AWS Marketplace place listing is pending, but you can launch the AMIs directly using the IDs below:

Region

AMI ID

ap-northeast-1

ami-a3ed72c5

ap-northeast-2

ami-01d5756f

ap-south-1

ami-9e7b2ff1

ap-southeast-1

ami-d71869ab

ap-southeast-2

ami-532cde31

ca-central-1

ami-d5e164b1

eu-central-1

ami-b58f1cda

eu-west-1

ami-867ceaff

eu-west-2

ami-e1e8f085

eu-west-3

ami-9a19aee7

sa-east-1

ami-d0d596bc

us-east-1

ami-628ad918

us-east-2

ami-2cf4df49

us-west-1

ami-6d03030d

us-west-2

ami-a0f247d8


See also Cloud and Teams/Cloud.