fix broken link

| Operation: | Notes: |

| ---------  | ------ |

| 1. Login via the frontend & select Sandbox tab | _See [frontend](../Sandbox-User-Interface#mec-sandbox-wireframe#SBox01)_ |

| 1. Login via the frontend & select Sandbox tab | _See [frontend](../Sandbox-User-Interface#mec-sandbox-wireframe#sbox01)_ |

| 2. Select the `dual-mep` network to deploy in the user sandbox | `dual-mep` scenario has `mep1` for Zone 1, 2 & 3 locality and `mep2` for Zone 4 locality <br><br> Each node runs an instance of Location service with its own dataset; RNIS & WAIS are MEC system wide services.

| 3a. Pre-configure MEC Application with Application Enablement service endpoints | Endpoints `mep1`: <br>- `https://try-mec.etsi.org/<my-sandbox-key>/<mep1>/mec_app_support/v1`<br>- `https://try-mec.etsi.org/<my-sandbox-key>/<mep1>/mec_service_mgmt/v1` <br> Endpoints `mep2`: <br>- `https://try-mec.etsi.org/<my-sandbox-key>/<mep2>/mec_app_support/v1`<br>- `https://try-mec.etsi.org/<my-sandbox-key>/<mep2>/mec_service_mgmt/v1`|

| 3b. Pre-configure MEC Application with an Application Instance ID (e.g. `appInstanceId`) | MEC Platform Manager (MEPM) usually assigns `appInstanceId` to running applications <br><br> To support external user applications, the `appInstanceId` has to be generated from the [frontend](../Sandbox-User-Interface#mec-sandbox-wireframe#SBox04)<br><br> Generating the `appInstanceId` asks for the locality of the MEC Application (e.g. `mep1` or `mep2`)|