Let’s take a quick look at the details:
We have AMIs for the majority of AWS regions. When you launch a new instance in the AWS EC2 Console, find the right one by searching for the relevant AMI ID under the Community AMIs tab. Note that new AMI versions are published about every month and include the date of publication in the AMI name.
Here’s a list of the AMI IDs by region:
Make sure the AMI comes from owner
If you don’t see your preferred region in the list above, contact our support team, and we’ll get one created for you!
When you launch an instance of the AMI, you’ll need to:
- Choose an instance type: use
- Enter a storage size: must be at least 16 GB; we recommend 75-150 GB for typical installs.
- Select or create a security group: open ports
8800(npm Enterprise admin UI).
- Select or create a
.pemkey pair: this allows you to
sshinto your server instance.
It’s not necessary, but if you’d prefer to attach an EBS volume for registry data that is separate from the root volume, you can. However, the root EBS volume cannot be smaller than 16 GB.
You don’t have to, but you can
ssh into your EC2 instance to make sure it’s up and running. If you do, you should see a welcome message like the following:
Open your favorite web browser, access your server on port
8800, and follow the prompts to configure and start your appliance.
For more information on configuring npm Enterprise, see Server Configuration.
That’s it! Once you’ve configured and started the appliance, your private npm registry and website are ready for use. See this document for configuring your npm CLI to use your new private registry.