Define roles and policies in AWS. In particular: A vmimport service role and a policy attached to it, precisely as explained in this AWS doc. Manual steps With the prerequisites satisfied the process is: Create your VM. Your vbox needs to have cloud-init installed and configured. RedHat based distributions include cloud-utils in the EPEL repo; the following script can be used to configure the expected login user as ec2-user :!
Note that the produced AMI will have some auto generated name and description; the ones we supplied in the aws cli command are used only by the import-image task. Automating the process The above steps can be tedious and since I needed to import vagrant boxes, I created a tool to automate this: amiimport.
Currently only virtualbox providers are supported. Very useful if the script is not run from another program. Conclusion Despite the fact that AWS public AMI store is very rich in images, there are always corner cases where you need to create something from scratch. We're hiring. For this reason, we are documenting the steps that we use to generate this default image, below. The following steps go through setting up an image using Ubuntu Linux. If you prefer, you can also host Relativity Server on a Windows image, but there is little benefit to that, and Windows EC2 instances will be more costly to run.
Note : Once again, these are not steps you will normally need to take care of yourself, if you use the provided images. You can now boot new instances from this image, publish it or share it with other members of your team. Note : We destroy the key file used to set up the publicly available Relativity Server AMI images , so you can be sure that nobody , including us, can ever access your live instances. Data Abstract. We use the "general purpose" instance.
In general there are two ways to build AMIs: Spinning up a new instance, customize it and create a snapshot or build the AMI from scratch. The first option seems to be the most common case.
This breaks the clean separation of build- and runtime and might mess up your build artefacts. Sure, you can clean up those things but I prefer avoiding it in the first place by never entering the runtime before actual deployment. Maybe it sparks the interest in building some good tooling around that - or maybe I get to it at some point. Creating a PV image is simple.
Now you you can mount that image, install your OS debootstrap comes handy and create a menu. You probably also want to install cloud-init to take care of your networking and fstab setup.
0コメント