...
To demonstrate how this transition can be done, we have an instance that has been launched in the qh2-uom-internal network and can only be accessed from the private network.
In the Actions column, click on the drop down arrow for the instance and click on Detach Interface.
In the Port field, there will be only one value - the IP address for that instance. Select it and click on Detach Interface to remove the instance from it's current network i.e. qh2_uom_internal.
After detaching this (network) interface, the instance will NOT have an IP address associated with it (and security groups will be removed as well). This indicates that it has been removed from the qh2_uom_internal network. Now, you need to add it to the qh2_uom network. To do so, in the Actions column, click on the drop down arrow for the instance and click on Attach Interface.
Keep the default values except for the Network field - you must specify the network to which this instance needs to be a part of - which is qh2-uom in our case. Click on Attach Interface.
The instance has now moved to the public qh2_uom network and will have a different IP address associated with it. Since a new interface was attached to the instance, only the default security group will be attached to it - so add the relevant security group(s) to the instance as per your use case. Note that your instance is now accessible world-wide, apply the necessary security groups to keep it secure and minimize cyber-attacks.