When prompted to login using a root account or IAM user, select IAM user.
Use the account ID, username, and password you collected at the beginning of the lab to login to your AWS console
Locate resources in AWS
From the AWS console, change your region to US East (N. Virginia) us-east-1 (this is where your gitlab resource lives)
From the Services menu at the top of the AWS console, select Compute and then EC2
Under the Resources heading, click Instances (running)
You will see two resources:
- Your Gitlab Server (SSEGitLabServer) - this is the resource we will be accessing “internally” via SSE.
- Your SSE Private Access PoP (SSEv2PoPServer)- This is what connects your internal environment(s) to the Skyhigh SSE mesh.
Collect the internal DNS name of your GitLab server
In the Instances list, click the Instance ID next to your SSEGitLabServer entry.
Record the Private IP DNS name for this machine - you will need it in an upcoming section
Optional: In your remote desktop connection, visit http://your-gitlab-private-dns-name and verify that is presently inaccessible
Locate your SSE MicroPoP in the Skyhigh SSE console
In your Skyhigh SSE console, click the configuration gear and select Secure App Connector
You’ll see one healthy PoP instance, which is the “WorkshopPoP-A” EC2 Instance you just viewed in the AWS console.