Ticket #1167 (closed task: fixed)

Opened 3 years ago

Last modified 3 years ago

Create a standard CKAN system image for Amazon EC2 (AMI)

Reported by: nils.toedtmann Owned by:
Priority: awaiting triage Milestone:
Component: ckan Keywords:
Cc: rgrp, thejimmyg, pudo, dread Repository: ckan
Theme: none


We should create a public AMI with CKAN pre-installed and configured such that users can easily create their own EC2 machine with a running CKAN to play with.

There are three phases:

  1. [nils] Deploy an empty EC2 instance to become the CKAN image master instance
  2. Install a CKAN and give it a standard configuration.
  3. [nils] Create a AMI from the CKAN image master instance and publish it.

I am happy to do first and last. Who is installing and configuring CKAN?

Unfortunately AMIs are specific to region, architecture and storage type. We cannot maintain too many images, so a number of choices have to be made:

  • Which distribution/version? Ubuntu 10.04 LTS
  • Which architecture/instance-type? I suggest 64-bit/t1.micro
  • Which region? I suggest us-east-1 and maybe eu-west-1
  • Which storage type? EBS (way easier to make an AMI from than instance-store)
  • Install CKAN from deb packages via mercurial/virtualenv? I assume the latter because the AMI is targeted to developers?

1 2

Change History

comment:1 Changed 3 years ago by sebbacon

Yes to all the above.

Further question: which extensions should be installed as standard? I would argue:

  • ckanext-stats
  • ckanext-googleanalytics
  • ckanext-disqus
  • ckanext-solr (implies installing a running solr, too...)
  • ckanext-follower
  • ckanext-admin

Note that googleanalytics and disqus both require user accounts set up at the corresponding service. Not sure how we would handle this in the instance setup.

comment:2 Changed 3 years ago by sebbacon

Another thing to consider: how do we ensure we keep a single, up-to-date version available? (I'm thinking wrt developer / sysadmin workflow)

comment:3 Changed 3 years ago by thejimmyg

Creating the AMI is really just the icing on the cake. The hard bit is getting the packaging right so that's where we need to concentrate first. Once the packaging works we just make sure apt-get upgrade is run regularly.

+1 to the list above.

I also agree we should install solr by default. Who has actually done a CKAN solr install? I haven't but together with whoever has I can try to package it up.

Wrt to usernames and passwords, I'll look into how dpkg manages those blue pop-up screens for entering configuration options.

comment:4 Changed 3 years ago by dread

  • Cc dread added

debconf seems the preferred way to question the user post-install and run setup scripts. It seems a bit of a faff.

The person that is able to spin up an EC2 instance is no doubt technically able enough to follow a couple of instructions in README.txt saying edit /etc/ckan/<instancename>/<instancename>.ini and add your Google Analytics credentials. So I don't think this ticket is the driver for a debconf setup.

comment:5 Changed 3 years ago by thejimmyg

  • Status changed from new to closed
  • Resolution set to fixed

I've now written a 20 page guide on using CKAN on Amazon EC2. I haven't explicitly created an AMI, but I don't think we should do that anyway for a few reasons:

  • it is fiddly
  • there is no advantage to the user as CKAN installation is so easy and so well documented
  • we don't want to have to maintain the image going forward
  • we might not want to promote a non-open approach

The guide will form part of Anna PS's work on the overall documentation but you can also see the original version here:


Note: See TracTickets for help on using tickets.