Over a million developers have joined DZone.

Run Nexus OSS 2.0.1 on Amazon EC2

· Cloud Zone

Download the Essential Cloud Buyer’s Guide to learn important factors to consider before selecting a provider as well as buying criteria to help you make the best decision for your infrastructure needs, brought to you in partnership with Internap.

We cut an simple EC2 image with Nexus OSS 2.0.1 running on Ubuntu 2.0.1. If you are thinking about adopting a repository manager, Nexus OSS is often the first step in this journey. While most of our audience downloads Nexus to a workstation to try it out, several of you have asked for EC2 images over the past few years. Here’s a video that demonstrates how you can use a pre-made EC2 image that automatically starts Nexus and makes is possible to get up and running in minutes. 

To use this image:

  1. Sign into your AWS Management Console.
  2. Click on the EC2 tab.
  3. Click on Launch Instance.
  4. Select the Classic Wizard and click Continue.
  5. When selecting an AMI, click on Community AMIs and then search for “sonatype”. This search tends to take a minute (or longer).
  6. Once the search is complete, you should see an AMI with the following identifiers (select this AMI):
    • AMI ID: ami-14aa727d
    • Manifest ID: sonatype-nexus-2.0.1-ubuntu-10
  7. We recommend running Nexus on an m1.small instance (or higher).
  8. There is no special configuration other than the security group…
  9. Make sure that the Security Group for this instance allows inbound TCP on ports: 80, 22, and 8081.
  10. That’s it. Launch the instance.

Once you’ve launched the instance, it takes about 3-4 minutes for the instance to startup. Copy the public hostname and go to “http://:8081/nexus” in a browser. Login with the default administrator credentials: admin/admin123.

This instance has had as little customization as possible. It is a stock Ubuntu 11.10 instance, Nexus is installed in /opt, there is a Nexus user, and Nexus is configured to startup automatically. There has been no effort to secure or lock down this machine.

If you do end up depending on this image as a foundation for your own production instance of Nexus OSS you will likely want to do three things:

  • Change the default password for Nexus (that’s a must).
  • Secure the machine. Whether this means locking down inbound and outbound access with a firewall or putting the machine on an Amazon managed VPN, this is entirely up to you. Just understand that you are on your own when it comes to instance security – we’re just publishing a template.
  • Mount an EBS volume and move /opt/sonatype-work to it. This machine doesn’t have much space to work with, and the storage that comes with an instance (on /mnt) isn’t the most reliable storage around. With an EBS volume you’ll get something you can take a nightly snapshot of and a volume that will survive instance termination.

That’s it for now, if you find this useful, please let us know. We’d like to make it as easy as possible for people to start using a repository manager and this is part of that overall effort.

The Cloud Zone is brought to you in partnership with Internap. Read Bare-Metal Cloud 101 to learn about bare-metal cloud and how it has emerged as a way to complement virtualized services.

Topics:

Published at DZone with permission of Tim O'brien, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}