How to import the OVF in Amazon Web Services (AWS) EC2
Below the steps to load SWS appliance on Amazon Cloud:
1) Download and install AWS CLI from this link (https://docs.aws.amazon.com/en_us/cli/latest/userguide/cli-chap-install.html)
2) Execute AWS CLI with the command aws configure
3) Load the virtual machine disk (.vmdk) on S3 bucket using this command of AWS CLI:
Code Block |
---|
|
aws s3 cp "<vmdk-path>" s3://<nome-bucket-S3>/
Example → aws s3 cp "C:\Users\utente\Desktop\SWS\Disk.vmdk" s3://my-bucket-S3/ |
4) When the loading is complete, create the AMI with this command
How to import the OVF into VMware Workstation Player
For importing the OVF, you can follow these steps:
- Download VMware workstation player from this link: https://www.vmware.com/products/workstation-player.html
- Install VMware workstation player and open
- Go to: File → Play → Open → select the OVF just downloaded
How to import the OVF into VirtualBox
For importing the OVF, you can follow these steps:
- Download VirtualBox from: https://www.virtualbox.org/
- Install VirtualBox and open
- Go to: File → Import Virtual Appliance → select the OVF just downloaded
How to import the OVF in Amazon Web Services (AWS) EC2
Below the steps to load SWS appliance on Amazon Cloud:
1) Download and install AWS CLI from this link (https://docs.aws.amazon.com/en_us/cli/latest/userguide/cli-chap-install.html)
2) Execute AWS CLI with the command aws configure
3) Load the virtual machine disk (.vmdk) on S3 bucket using this command of AWS CLI:
Code Block |
---|
|
aws s3 cp "<vmdk-path>" s3://<nome-bucket-S3>/
Example → aws s3 cp "C:\Users\utente\Desktop\SWS\Disk.vmdk" s3://my-bucket-S3/ |
4) When the loading is complete, create the AMI with this command: Code Block |
---|
|
aws ec2 import-image --description "SWS AMI" --disk-containers "Format=vmdk,UserBucket={S3Bucket=<nome-bucket-S3>,S3Key=<vmdk-path>}"
Example -> aws ec2 import-image --description "SWS AMI" --disk-containers "Format=vmdk,UserBucket={S3Bucket=il-mio-bucket-S3,S3Key=Disk.vmdk}" |
5) Now is possible to monitor the AMI creation with this command: Code Block |
---|
|
aws ec2 describe-import-image-tasks |
6) When the AMI creation is complete, will be available at this path:
EC2 Section → Images → AMIs
Now is possible deploy EC2 instance.
At step 1 and 2 describe how install aws client on the workstation that will be used for all the import activity of the application solution. The aws client just created will be used for next steps.
At step 3 the data disk (vmdk file) of the sws appliance is loaded. Usually the data disk is called "swsappliance-release-number-sws-1.vmdk" the disk in order to be imported must be loaded on an s3 bucket of the customer who can freely choose among those he has or can create at the moment. The latter will be used to convert the data disk from vmdk files to the native AWS format
At step 4 the disk conversion takes place and the values between <...> must be replaced with those that the customer has chosen to use:
Code Block |
---|
|
aws ec2 import-image --description "SWS AMI" --disk-containers "Format=vmdk,UserBucket={S3Bucket=<S3<nome-bucket-name>S3>,S3Key=<vmdk-path>}"
ExampeExample -> aws ec2 import-image --description "SWS AMI" --disk-containers "Format=vmdk,UserBucket={S3Bucket=swsrocksil-mio-bucket-S3,S3Key=swsappliance-2-5-33-1.vmdk}"
|
At this step the vmdk file remains in the bucket, but an AMI with description SWS AMI is created in the default region with which aws cli has been configured (it is set when the client configuration is carried out at step 2)
At step 5 is possible to monitor the procedure started at step 4 (because this step is very slow)
At step 6 is possible to monitor from AWS panel console if the AMI has been imported correctly and is ready to be used.
After the import has been completed, you start the virtual machine and configure the parameters via "Menu Console".
Image Removed
This menu allows to set parameters such as proxy, NTP etc. The options of the menu are:
- Register: VA registration to our centralized update system (SCM)
- Config: IP ADDRESS, GATEWAY, DNS and ROOT PASSWORD configuration
- Update: Updates installation (system and push updates)
- Proxy: proxy configuration NTLM and port
- Restart_jboss: restart of the application server SWS
- Restart_osad: restart of sync module VA/SCM
- Reboot: VA restart
- Shutdown: VA shutdown
- Logout: exit from Menu Console
- Exit: go to Bash shell*
*This option must be selected under the monitoring of a Namirial operator. Namirial doesn’t give any support about modifications executed without WEB interface or Console Menù
Proxy properties: specify credentials user and password
If you use proxy with specify username you must follow this step:
- Login SSH to appliance
- Execute this command for set proxy username:
Code Block |
---|
sudo /opt/wildfly/bin/jboss-cli.sh -c --command="/system-property=proxyUser:add(value=PROXY_USERNAME)" |
Execute this command for set proxy password:
Code Block |
---|
sudo /opt/wildfly/bin/jboss-cli.sh -c --command="/system-property=proxyPassword:add(value=PROXY_PASSWORD)" |