MaxMind GeoIP libraries and database on Amazon Elastic Beanstalk

Question

I'm trying to figure out how to install and use GeoIP libraries on AWS (Elastic Beanstalk). As far I know EB has an "ephemeral filesystem", but I could store the CeoCity binary in S3… but what about MaxMind C libraries? Has anyone configured EB to use MaxMind's api?

(My stack is based on Python/Django)

Yes, but I created my own custom AMI, see my blog post: http://www.daveoncode.com/2014/02/18/creating-custom-ami-with-postgis-and-its-dependencies-to-deploy-django-geodjango-amazon-elastic-beanstalk/ (after installing all the necessary libraries I copied the GeoCityLite.dat under /etc/ in my AMI) — daveoncode, Mar 07 '14 at 08:31

georgiecasey · Answer 1 · 2015-06-08T03:30:04.610

I don't know why you'd bother customising an AMI when a simple .ebextensions script would do the job with the added advantage of downloading a fresh Maxmind DB with every deploy. Note that my example script is hardcoded to the latest GeoIP client code as of today so you might want to upgrade this every now and then. But I doubt there'll be huge changes to the client code so it'll always work. This script is for the PHP API and free GeoLite2 databases, it's easy to change out for Python client code.

files:
  "/usr/local/bin/geoip2.phar" :
    mode: "000644"
    owner: root
    group: root
    source: https://github.com/maxmind/GeoIP2-php/releases/download/v2.1.1/geoip2.phar

  "/usr/local/share/GeoIP/GeoLite2-City.mmdb.gz" :
    mode: "000644"
    owner: root
    group: root
    source: http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.mmdb.gz

  "/usr/local/share/GeoIP/GeoLite2-Country.mmdb.gz" :
    mode: "000644"
    owner: root
    group: root
    source: http://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.mmdb.gz

commands:
  gunzip_maxmind_city:
    command: gunzip -f GeoLite2-City.mmdb.gz
    cwd: /usr/local/share/GeoIP
  gunzip_maxmind_country:
    command: gunzip -f GeoLite2-Country.mmdb.gz
    cwd: /usr/local/share/GeoIP

score 0 · Accepted Answer · answered Feb 05 '14 at 09:30

0

I believe you have two options to handle situations where new EC2 instances are being created automatically for you:

Either create a custom AMI for your EC2 instances, or
Customize your AWS EB environment.

Amazon issues a notice about using custom AMI:s:

"After you are running on your own custom AMI, you will no longer receive any 
automated updates to the operating system, software stack, or the AWS Elastic 
Beanstalk host manager."

Personally, I've stuck to using configuration files. Takes a bit of tinkering, but once I got it working it operates pretty well.

Good luck!

answered Feb 05 '14 at 09:30

joker

746
4
11

eheh… The point is: I'm using elastic beanstalk, since I don't want to configure an AMI by myself :P – daveoncode Feb 05 '14 at 10:13
I can definitely see why not. Just note that customizing your AWB environment through EB config files isn't the same thing as rolling your own AMI. – joker Feb 05 '14 at 11:48
In the end I created my own custom AMI :P – daveoncode Mar 07 '14 at 08:27

score 0 · Answer 3 · answered Feb 10 '14 at 22:46

An alternate approach would be to use AWS EB to attach a snapshot of an EBS volume.

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-as-launchconfig-blockdev-mapping.html

Whenever an environment is created with this setting, the nivolved instances will get it attached. from this point, you can, say, take it over with .ebextensions.

(It also allows you to map ephemeral volumes on instances supporting eg m1.small)

MaxMind GeoIP libraries and database on Amazon Elastic Beanstalk

3 Answers3