Sometimes, we need to make developments, customizations, and more in our local VMs and later on, we realize that the same developments would be great to have in the cloud as well. Therefore, this documentation will demonstrate how we can do such a task by using Bahmni Vagrant and AWS as cloud provider via its VM Import/Export feature.
| Note |
|---|
Warning: 1. Using this feature will cost you money on AWS, therefore please make sure to check and terminate any resources that you don’t need anymore once you finish testing. 2. Cloud based systems are public, and hence at risk. Please ensure you setup firewalls, fail2ban, security groups/ACLs, private subnet, etc to keep your machine safe. Read more in the Bahmni Security Guide. |
| Table of Contents |
|---|
STEP 1: Exporting the VMs Image
...
Now we have an OVA file which is basically the image that can be used for exporting to the AWS.
note: You can execute the same task with your VMs that are running on a VMware® vSphere as well. What you need to know is that these VMs must be exported in one of the supported versions. For a list of supported versions, please follow this link.
...
| Code Block |
|---|
aws iam put-role-policy --role-name vmimport --policy-name vmimport --policy-document "file://role-policy.json" |
note: Ensure that the name of the S3 bucket must be the bucket you've created on AWS. If you cannot create the bucket or execute any command, please refer to the documentation above because most probably you have some permission settings that are different, or the AWS CLI isn't installed properly.
...