Transitioning from qh2-uom-internal to qh2-uom public networks
Context
If your instance currently uses a private IP but you need it to be accessible from the public Internet, then you need to transition it to the public qh2-uom
network.
First request and receive approval from the UoM Cyber Security Team.
Then use this guide to transition the network.
Please ensure you adhere to the listed security guidelines and familiarise yourself with the operational guidelines.
Guide
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. The next step will be to add it to the qh2_uom
network.
Â
In the Actions column, click on the drop down arrow for the instance and click on Attach Interface.
Â
Â
Keep all the default values except for the Network field - update the network to
qh2-uom
. Click on Attach Interface.
Â
IMPORTANT: Your instance is now accessible world-wide, so you need to apply the necessary security groups to keep it secure and minimize cyber-attacks.
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 be sure to add the relevant security group(s) to the instance as per your use case.
Â
Â
Â