Publishing to a remote AMI instance on the Amazon Cloud

If you recall, WEF and portal development cloud were chosen as the development paradigms for the A2Z portal. A2Z portal application developers and specialists generate and customize their portlets on their local WEF unit test environment and load them to the development cloud for further development with the other integrated components, such as global security. They are expected to move their portlet application from their local systems to a remote development cloud, an Amazon Machine Image (AMI) instance. With the image used during the POV as a template and others provisioned within minutes, A2Z portal and cloud administrators instructed WEF specialists to perform the following steps to publish their portlet application to the remote AMI instance:

1. 1. They edited their local systems hosts file and mapped the AMI public and internal host names in their hosts file (usually located at C:\WINDOWS\system32\drivers\etc\hosts or /etc/hosts...