The only down side of this would be any secrets stored in any SSM
Parameter Store locations, but at this point in time I don't think three
are any; historically, people would store secrets into S3 buckets
(probably client-side encrypted, definitely server side encrypted).
These secrets could be
Here's some updated images for Jessie.
|| '''Region''' || '''hvm x86_64 ebs''' ||
|| ap-northeast-1 || ami-dbc0bcbc ||
|| ap-northeast-2 || ami-6d8b5a03 ||
|| ap-south-1 || ami-9a83f5f5 ||
|| ap-southeast-1 || ami-0842e96b ||
|| ap-southeast-2 || ami-881317eb ||
|| ca-central-1 || ami-a1fe43c5
Hello all,
Just getting my head above water after the last sprint (and subsequent
catch up at work) one of the issues present was a refresh for the
EC2 images taking in the latest kernel packages addressing the Dirty Cow
bug, also known as CVE-2016-5195. Its important that our booting kernels
Hm. Closest I had got was setting the Cache Control headers really low -
so it was supposed to be rare. Perhaps 5 minutes on "sid" as a default
is too long?
The timeouts we have are:
ExpiresDefault "access plus 30 minutes"
On 4/11/2016 10:28 PM, Tim Sattarov wrote:
> Just checked on one of the instances:
> dmidecode shows
>
> BIOS Information
> Vendor: Xen
> Version: 4.2.amazon
> Release Date: 05/12/2016
>
>
> and dmesg
> [6.352070] xenbus_probe_frontend: Waiting for devices to
Let's try this for the nth time and see if it gets through to the list! ;)
Forwarded Message
Subject:ASW EC2: Debian Jessie 8.6 AMIs for beta testing...
Date: Tue, 20 Sep 2016 23:05:51 +0800
Hello all
(Hoping this message gets to list, as previous months have not)
On 3/05/2016 10:34 PM, Marcin Kulisz wrote:
> On 2016-05-03 15:25:40, Steve McIntyre wrote:
>> I know that some people won't be able to make this session, but it
>> would be good to get some discussion anyway. If you have any input,
>> please let us know.
> I'm not able to go to this year DC, so
Hello all,
Here's a bunch of images for Debian 8.4 in the main commercial AWS EC2
regions:
|| '''Region''' || '''hvm x86_64 ebs''' ||
|| ap-northeast-1 || ami-d7d4c5b9 ||
|| ap-southeast-1 || ami-73974210 ||
|| ap-southeast-2 || ami-09daf96a ||
|| eu-central-1 || ami-ccc021a3 ||
|| eu-west-1 ||
On 13/03/2016 9:33 PM, Charles Plessy wrote:
> Le Sat, Mar 12, 2016 at 10:40:30PM +0800, James Bromberger a écrit :
>> On 12/03/2016 9:19 PM, Charles Plessy wrote:
>>> The Debian images on the Amazon cloud are of the "minbase" variant, and
>>> extra
>>
On 12/03/2016 9:19 PM, Charles Plessy wrote:
> The Debian images on the Amazon cloud are of the "minbase" variant, and extra
> packages are added. (James, I lost track on where to find this information in
> the source code of bootstrap-vz, or on the Debian wiki, can you remind me the
>
On 10/03/2016 6:22 PM, Charles Plessy wrote:
> Le Thu, Mar 10, 2016 at 10:18:30AM +0100, Bastian Blank a écrit :
>> On Wed, Mar 09, 2016 at 11:51:58PM +0900, Charles Plessy wrote:
>>
>>> Maybe this problem can be solved by the use of metapackages ? With the
>>> exclusion of cloud-init,
On 17/02/2016 11:17 PM, James Bromberger wrote:
> |AMI generated in US East 1 and shared publicly: |ami-f0e7d19a
>
And now of the rest of the world:
ap-northeast-2: ami-4a2ae424
us-west-2: ami-837093e3
us-west-1: ami-f28bfa92
sa-east-1: ami-651f9c09
ap-northeast-1: ami-899091e7
eu-west-
On 17/02/2016 10:06 AM, Charles Plessy wrote:
> Le Tue, Feb 16, 2016 at 01:54:04PM -0200, Tiago Ilieve a écrit :
>> The backport for "cloud-utils" has arrived at the archive[1].
> Hi,
> the backport of cloud-init is there as well :)
> Have a nice day,
>
Awesome. Many thanks Charles and Tiago.
On 31/01/2016 1:32 AM, Tiago Ilieve wrote:
> About the growpart issue that we talked about, I proposed a
> backport[1] for "cloud-utils" on #784004. I don't know if it will be
> accepted (and I do remember that you don't like to rely on fixes from
> backports, that's why I didn't asked you to
Hello all,
After some time, we now have a Jessie 8.2 image, now working with
systemD, gtp formatted volume, updated ixgbevf driver, blacklists a few
module to trim some time, and updated cloud-init config to set ephemeral
disks it discovers as "nofail" in the fstab (eg, for when you resize
Hi all,
I've had some contact with the team from Oracle who are looking for a
way to get official Debian images into the Oracle Cloud. They'd like to
hire a Debian developer who will work for/with them to create and sign
off on Debian images on their platform. I don't have the time to take
this
On 23/06/2015 3:36 PM, Marcin Kulisz wrote:
On 2015-06-23 00:09:01, Klas Meder Boqvist wrote:
Hi
Hi
Is it possible to have different names on the jessie images on AWS
marketplace depending on if they are hvm or paravirtual?
It's hard to see any difference, when the names and descriptions
On 16/06/2015 4:03 AM, Anders Ingemann wrote:
On Mon, Jun 15, 2015 at 7:16 PM Christophe Bernard
christophe.s.bern...@gmail.com
mailto:christophe.s.bern...@gmail.com wrote:
Hi all,
I have instanciated the Jessie AMI
https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie
at 10:34:49PM +0800, James Bromberger wrote:
|| eu-central-1 || ami-02b78e1f || ami-5cb78e41 ||
Sorry to repeat myself, but this image still has the ed25519 bug.
Could we please have this bug fixed in jessie, whatever is the package
that it is causing it? (cloud-init maybe, I don't know).
I've
Hello all,
Here's some updated Jessie images for the 8.1 point release in all Regions:
|| '''Region''' || '''hvm x86_64 ebs''' || '''paravirtual x86_64 ebs''' ||
|| ap-northeast-1 || ami-e624fbe6 || ami-0822fd08 ||
|| ap-southeast-1 || ami-ac360cfe || ami-4e370d1c ||
|| ap-southeast-2 ||
On 19/05/2015 4:16 AM, Ognyan Kulev wrote:
Hi,
Currently, Debian HVM image is shown in AWS marketplace like the
following and I would like to suggest minor improvements:
Debian GNU/Linux - (HVM)
* (1) | Version 8.0.0 | Sold by Debian
...
Linux/Unix, Debian 8.0.0 | 64-bit Amazon Machine
for Amazon anymore)
maintained by James Bromberger. What I found closer to this are those
boxes[2] provided by Kraksoft[3]. The scripts used to generate it are
available at their repository[4].
... are maintained by me! :) . Yes, not working for AWS now, but still
maintaining these and pushing them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Time for a quick refresh on the Jessie images... introducing the
20150213 images in all regions.
20150213
Region hvm x86_64 ebsparavirtual x86_64 ebs
ap-northeast-1ami-d9ee08d9ami-d1e305d1
ap-southeast-1ami-e49faab6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
I've refreshed the Jessie AMIs in all regions as shown at
https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie, and hereby listed
(and this message is signed):
|| '''Region''' || '''hvm x86_64 ebs''' || '''paravirtual x86_64 ebs''' ||
||
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
I've refreshed the HVM 64 bit Jessie images corresponding to the start
of the Jessie freeze!
|| '''Region''' || '''hvm x86_64 ebs''' ||
|| ap-northeast-1 || ami-89e5de88 ||
|| ap-southeast-1 || ami-f2496ba0 ||
|| ap-southeast-2 ||
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/11/2014 8:56 AM, Brian Gupta wrote:
On Mon, Nov 3, 2014 at 11:49 AM, James Bromberger ja...@rcpt.to wrote:
Second, with all current-generation instance types being HVM capable, I am
going to suggest we no longer generate Paravirtualisation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
It was brought to my attention that the experimental Wheezy HVM AMIs
(using extlinux in stable due to grub bugs/issues in Debian stable) that
the bootloader was set to quiet and thus not passing some useful debug
to the console. I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
We're fast approaching the big freeze[1], so I wanted to start to
summarise up the status of the EC2 AMIs.
Thanks to Eric Evans, Python-Boto 2.33 hit testing in the last few days.
This represents a huge step forward from Wheezy's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
Following on from the opening of the new Amazon region in Germany, here
are the Debian Wheezy 7.7 AMIs for this location:
AMD64, HVM, EBS Backed: ami-482a1c55
i386, PVM, EBS Backed: ami-522a1c4f
AMD64, PVM, EBS Backed: ami-4c2a1c51
Hello all,
With Wheezy 7.7 out the door today.. here come some new AMIs:.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Debian Wheezy 7.7 AMIs, 18 October 2014:
|| '''Region''' || '''hvm x86_64 ebs''' || '''paravirtual i386 ebs''' ||
'''paravirtual x86_64 ebs''' || '''paravirtual x86_64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
With the second update to Wheezy 7.6 (thus denoted 7.6.aws.2), I'm going
to retire the older 7.6 (original release) and 7.6.aws.1 (first bash
fix) in around 3 weeks time on 31 October 2014. This is the same day
that AWS EC2 Debian Wheezy
backed images?
I use them a lot
On 28 September 2014 03:46, James Bromberger ja...@rcpt.to
mailto:ja...@rcpt.to wrote:
Pause that, the 2nd updated bash package hadn't propagated in time, so
here's an updated set of base AMIs:
|| Region || i386 || x86_64 || x86_64
On 28/09/2014 12:27 PM, Brian Gupta wrote:
Thank you, thank you!
Welcome!
;)
How do we deal with all the AMIs out there with this bug? (This isn't
just a Debian/AWS question). I wish there was a way to replace them
without changing their IDs. /sigh
We recommend apt-get update, apt-get
/Cloud/AmazonEC2Image/Wheezy.
Thus the Wheezy 7.6.aws.1 will now be deprecated, and I'll remove them
end of next week (Friday 3rd October).
James
On 26/09/2014 4:18 PM, James Bromberger wrote:
Hello all,
Following the recent bash bug of CVE CVE-2014-6271 and CVE-2014-7169,
I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello all,
Following the recent bash bug of CVE CVE-2014-6271 and CVE-2014-7169,
I have generated fresh AMIs for EC2 that should contain the updated
bash package. These new AMIs are in all Regions, including Bejing and
US-GovCloud, and are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
I have generated a set of Debian Jessie AMIs in all AWS Regions
worldwide (8 standard commercial Regions, Beijing and US GovCloud).
These images are 64 bit, HVM only (using grub). They successfully boot
on all instances I have tested
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
This email is notice that I plan to remove the outdated 7.5 AMIs
(replaced by 7.6 AMIs back on 21 July 2014, 2 months ago) on 31st
October 2014.
Any CloudFormation templates and/or AutoScale groups that reference
these deprecated AMIs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
Here we go with Squeeze 6.0.10 AMIs in all standard Regions, and now
including US Gov Cloud as well for the first time (PVM EBS Backed AMIs).
Region 32-bit PVM 64-bit PVM
US-East-1 ami-5614da3eami-5e12dc36
Hello all,
I'm going to call time on the Debian Wheezy 7.4a AMIs (released in
response to the heartbleed vulnerability back on 8 April 2014); these
have now been superseded by both 7.5 back on 26 April 2014, and now 7.6.
I intend to remove public access from this old outdated AMI on Saturday
30th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/06/2014 8:10 PM, Tomasz Rybak wrote:
Exactly. For NBDs and loopback volumes, this is necessary when using
grub 1.99, because grub tries to be smart about things and then trips
over its own feet.
To avoid that, we fool grub into thinking
On 23/04/2014 11:09 PM, Brian Gupta wrote:
My initial take is that this seems a reasonable approach, if we
packaged it for sid, and make a backport. However, I would be curious
to know if (and how) Ubuntu handles this, as coordinating efforts here
might be useful?
I fired up an Ubuntu image,
Hi all,
Sorry for the delay in my response - been caught up teaching and just
jumped across Australia today.
The 1GiB is perhaps a little too small - especially on an m1.small host
with no other instance store disks. 10GiB is listed as the maximum for
S3 baked instances... but my rushed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Debian cloud,
Following on the release of Debian 7.4 earlier this weekend, I am
pleased to produce the updated list of AMIs in all EC2 Regions
worldwide, with the current exception of US Gov Cloud which will
hopefully happen over the course
Hello all,
I'd like to propose the end of life for the availability of the Debian
7.1a AMIs in all Regions. These 7.1a AMIs have been superseded for some
time by newer Debian releases (following the switch to Cloud-Init).
With the release today of 7.4 and corresponding EC2 AMIs, I am declaring
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
So I have been bashing away on S3 - and I have a working image in US
East 1(minor build-debian-cloud patches in the next few days). If you
want to have a play:
* PVM, 64 bit, S3 backed, US East 1: ami-79fcc510
(S3 backed HVM is giving
I finally managed to get HVM images working on EC2!
Currently they are booted with extlinux as I am still having some
trouble installing grub.
There is a sample manifest in the build-debian-cloud manifest folder
you can try out.
So far I have only tried with an unpartitioned volume.
On 14/01/2014 10:20 PM, David Osborne wrote:
Although I can see these images if I do a aws ec2 describe-images
--owners 379101102735 (from eu-west-1), I still can't see them via
the AWS GUI in AWS Marketplace when I either search for Debian, or the
debian account number.
Should they be
On 27/12/2013 9:18 PM, Anders Ingemann wrote:
Great stuff! I didn't know they switched licenses, or is it only for
the python version?
I remember we switched to euca2ools so the bootstrapper was in line
with the DFSG.
AWSCLI is a new (in 2013) version for command line utils, totally hosted
on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/12/2013 12:24 AM, James Bromberger wrote:
Bits, 32 bit, 64 bit
---
US-East-1, ami-33a68f5a, ami-0da18864
US-West-1, ami-8ebd8dcb, ami-96bd8dd3
US-West-2, ami-6a98fc5a, ami-7298fc42
EU-West-1, ami-66836b11, ami
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
I have done some more patches to build-debian-cloud (pull req with
Anders), and the new AMIs now boot much faster than what we saw for 7.2
and don't try and check for modules for which we don't want. So the list
of AMIs in this signed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/12/2013 6:09 PM, Chris Fordham wrote:
I gave it a real quick test.
I noticed the following:
[] Starting Cloud service: cloud-initCloud-init v. 0.7.2 running
'modules:config' at Tue, 17 Dec 2013 09:20:23 +. Up 139.74 seconds.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
It was already scheduled, and marked on the wiki for some months, but I
am going to remove the outdated 7.0.0 AMIs from being shared from the
Debian account tomorrow, 18 December 2014, and delete them shortly after.
My plan is to sort
Hello all,
Last night I generated a 32 and 64 bit AMI in US East 1 of Debian 7.3
[1], using the python scripts[2] (which have had more updates, thanks
all) and including cloud-init[3]:
AMD64: ami-4309272a Wheezy 7.3 base amd64 ebs
i386: ami-af0927c6 Wheezy 7.3 base i386 ebs
These (and their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/12/2013 9:20 AM, Paul Wise wrote:
Hi all,
At $work we're currently using cloudfront.d.n for the Debian mirror on
our EC2 servers. Are there any per-region Debian mirrors, as Ubuntu has?
We would prefer for our EC2 servers to only connect
I have been working on the cloud-init plugin over the weekend (and hvm
AMIs): https://github.com/andsens/build-debian-cloud/tree/python-WIP
I have not tested anything yet, but I am almost certain that there are
problems with the current AMIs.
The generate-hostkeys, authorized_keys and
, Nov 12, 2013 at 7:49 AM, Chris Fordham
ch...@fordham-nagy.id.au mailto:ch...@fordham-nagy.id.au wrote:
On Nov 12, 2013 1:10 AM, Felipe Reyes fre...@tty.cl
mailto:fre...@tty.cl wrote:
Hi James,
On Sun, Nov 10, 2013 at 10:33:46AM +0800, James Bromberger wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
So I've pushed what I think are the final patches into
build-debian-cloud that generate the EBS backed, PVM based, 32 and 64
bit AMIs. The main change here (other than shell - python) are:
* Backports is included in the sources.list
*
On 20/10/2013 1:38 PM, Charles Plessy wrote:
Le Mon, Oct 07, 2013 at 09:44:00PM +0800, James Bromberger a écrit :
After some more hacking on the python version of build-debian-cloud[1],
I have now generated a test AMI that supports cloud-init and no longer
uses the custom scripts that were
Hello Charles, world,
I am pleased to let you know that today AWS released PVGrub 1.04, with
support for gzip, bzip2, lzo, and xz compression formats. This also
supports GPT partitions (ie, large root volumes).
More information is here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Luke,
We (Debian) currently have only generated official PVM
(paravirtualization) based AMIs on AWS, and have yet to make an HVM
images - which is what the larger instance types require.
Right now I am slowly working on getting the switch to
On 9/07/2013 8:03 PM, Brian Gupta wrote:
On Fri, Jul 5, 2013 at 12:43 AM, James Bromberger ja...@rcpt.to wrote:
This leaves me with a question over the 7.0 release (which will have the
same ECC vulnerability). Should we deprecate (and remove) this? Feedback
required! ;)
As much as I would
On 10/07/2013 6:25 AM, Charles Plessy wrote:
Le Fri, Jul 05, 2013 at 12:43:33PM +0800, James Bromberger a écrit :
I am proposing to remove the following deprecated Debian AMIs:
* Debian Squeeze (base install AMI) *6.0.6*, 32 and 64 bit (PVM EBS
Root). This is *superseded by 6.0.7* which
On 5/07/2013 6:22 AM, Anders Ingemann wrote:
On 4 July 2013 16:59, Tormod Ryeng tor...@tormod.no wrote:
Ah, that's probably the bug, right there. I guess you'll need to remove and
generate /etc/ssh/ssh_host_ecdsa_key as well?
admin@ip-10-227-121-70:/etc/ssh$ ssh-keygen -lf
On 5/07/2013 9:22 AM, James Bromberger wrote:
Good morning all. I've grabbed the patch, and have generated a fresh
AMIs in US East 1, available now. I have launched two instances from
this, and confirm they successfully generated unique ECDSA host keys.
I'm currently replicating around
Hello all,
I am proposing to remove the following deprecated Debian AMIs:
* Debian Squeeze (base install AMI) *6.0.6*, 32 and 64 bit (PVM EBS
Root). This is *superseded by 6.0.7* which we will keep available as
the latest release from the 6.x.
* Debian Wheezy *7.1* (base install AMI)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/06/2013 4:04 PM, Stefano Zacchiroli wrote:
Yay! I'll be attending DebConf13 as well and will love to participate in
those events. Please remember to submit them to Penta though. At
https://penta.debconf.org/penta/submission/dc13/all_events
On 23/06/2013 10:18 AM, Brian Gupta wrote:
On Sat, Jun 22, 2013 at 10:10 PM, Eric Cooper e...@cmu.edu wrote:
On Sat, Jun 22, 2013 at 03:14:09PM -0700, Eric Hammond wrote:
You should be able to run any EBS boot AMI on a t1.micro under the
free tier.
If you run something through the AWS
HI Brian and all,
I've already been working with people on this, and right now it isn't an
option, but I am hoping to work on this over the next few months. I'd
welcome you sending me your account number(s) to jame...@amazon.com and
I can add your name to a list of AWS Debian customers who would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/05/2013 7:49 PM, Stefano Zacchiroli wrote:
As I understood it, that point is about the software that's contained in
the images. Am I wrong in assuming that euca2ools is only used to build
the images and not shipped as part of it? I've only
Hello all,
For the last week and a bit (just before Wheezy launch) we've been
testing out using Amazon's CloudFront CDN for distribution of CD Images
and the main Debian archive (ie, in apt/sources.list). With the latest
fix I have done, Ithink this is ready for a wider audience, so I'd like
to
On 11/05/2013 4:52 PM, Anders Ingemann wrote:
This is awesome! Great work!
Does pulling data from CF via an EC2 instance incur traffic costs?
Great question - and I promise this is not a set-up! Yes, but Amazon's
got it covered.
However, the charging pattern for this would be:
1) for the
Hello Steffan, Adam,
I think the question for cloud images becomes: would we consider a
Debian image with backports enabled in apt.sources *by default* and to
have packages installed from backports to still be 'pure' Debian? I
would think some would feel this is not.
This was much discussed
Yes, new AMIs for 7.0.0 'base' Debian, EBS Root, 32 64 bit for most
Regions are now updated on the wiki. Seems that using Copy AMI (from
Singapore) had an issue, so I went back to the original way of
generating each Regions AMI independently. Sao Paulo, I am working on
you next, but the rest of
On 5/05/2013 9:40 PM, Ian Hubbard wrote:
Would be great if we can get a few people to test. I'll be AFK for the
next few hours, but hope to pick up on Charle's Instance Store AMIs
this afternoon. HVM will have to wait to later in the week.
Hi,
I just tried to set up an instance in Sydney
Well done Charles. Great to see.
I'd like to poll the audience if I may about if we should pull
wheezy-backports into the sources.list of the EC2 AMIs, and/or if should
pull in cloud-init from backports for today/tomorrows base AMI builds?
Many may feel passionately that a base AMI should be
On 5/05/2013 11:09 AM, Charles Plessy wrote:
One solution would be to add wheezy-backports to /etc/apt/sources.list. By
default, it will never cause the installation of backports on the system
unless
the administrator specifically requests it.
One nice side effect of this is that other,
Hi Christian,
That's awesome!
- It requires euca2ools version 2.x because the commands that handle
image bundles are buggy in version 1.x.
Should this be a dependency on the build-environment, or downloaded by
this script? I think downloaded may be better, as in 2 years time,
stable euca2ools
On 31/03/2013 6:21 PM, Charles Plessy wrote:
Le Sun, Mar 31, 2013 at 03:07:09AM -0700, Brian Gupta a écrit :
Are there any plans to publish non-marketplace AMIs?
Hi Brian,
I think that it is done, see
http://wiki.debian.org/Cloud/AmazonEC2Image/Squeeze.
James, if you confirm, we can close
Hello all,
role name=debian-developer
I have just generated
fresh AMIs for the new point release of Squeeze released yesterday,
6.0.7 (see [0]). Anders has been kind enough to tag the
ec2debian-build-ami accordingly [1]. All these generated AMIs are pushed
as public, as are the underlying
Hello all,
Debian_hat
Following on from more work that Anders has done, I have regenerated
experimental test images of Wheezy in all AWS Regions (except GovCloud).
The new release has a source of:
* 379101102735/debian-wheezy-amd64-20130208
* 379101102735/debian-wheezy-i386-20130208
This
On 22/01/2013 6:17 AM, Anders Ingemann wrote:
Hey guys girls,
after some time off I have finally had the time to take a look at my
bootstrapper for Amazon Machine Images again and I am glad to announce
that it is now compatible with wheezy.
I would welcome anybody who would like to test the
81 matches
Mail list logo
