Context
If your instance currently uses a private IP and now needs but you need it to be accessible from the public Internet, then you need to transition it needs to be transitioned to the public qh2-uom network. Once your request is approved by
First request and receive approval from the UoM Cyber Security Team you can follow .
Then use this guide to transition the network.
| Info |
|---|
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. Now, you need The next step will be to add it to the qh2_uom network. To do so, in
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.
...
| Note |
|---|
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 |
| Info |
|---|
Please ensure you adhere to the listed security guidelines and familiarise yourself with the operational guidelines. |