#1821 Create alias for managing EC2 tasks.
Closed: Fixed None Opened 14 years ago by jforbes.

As a target for F13, we are looking at creating Amazon EC2 images which
Amazon will flag as "official Fedora releases". This is to counter the
problem where a user currently logs in and sees a choice of up to date
Ubuntu images or Fedora 8.
As a part of this process, we need to create an AWS account which will only
be used to store official AMI images, kernel images, and ramdisk images.
As such, a few people will need access to this account. Infrastructure
will need to manage those who can access this account, rel-eng will need
access for creating and pushing AMI images, and Kernel team will need
access for creating and pushing AKI/ARI (kernel and ramdisk images). A full
AMI is composed of the actual disk image, and an XML file which points to
an existing AKI and ARI.
To create this account, we first need an email address which can be used
for account administration, basic AWS sign up. The actual image creation
and upload is done with a numerical account ID and an Amazon provided key
pair. The basic account needs to be created fairly quickly so that Amazon
can apply kernel upload capability and put us on a free S3 pricing plan.
Obviosuly my redhat.com address is not the best choice for this address. I
was wondering if we could get a fedora specific alias that Infrastructure
could manage users under?


Just so I'm clear, here's what we're looking at.

1) Create an aws@fedoraproject.org
2) Create an amazon account that links to aws@fedoraproject.org

How do images actually make it to amazon for use, and how do they show up in the official list?

Done. aws@fedoraproject.org is the address, gets sent to members of the FAS group 'aws', owned by jforbes.

Login to comment on this ticket.

Metadata