Skip to content

Viewing Your Projects

View Projects

  1. From the time the project is requested and sent for admin approval, the project will be displayed on the My Projects page with a tag as 'Pending request'. Project card

  2. You can click on your project to see the details of the project that you have requested.

    Note

    While your project is in the Requested state, all modifications are disabled and the project remains read-only.

    Project detailed view

    Here, the following details are displayed:

    1. Project Details: Your project details like project name, description etc are available on the project details page.
    2. Users: Displays the number of users associated with your project.
    3. Region: Shows the number of GCP regions associated with your project.
    4. Budget: Provides budget-related insights and allocations for your project.
    5. Backup (Coming Soon): This section will offer backup and archival functionalities to ensure data retention and recovery.
    6. Cost (Coming Soon): Will include detailed cost tracking, usage insights, and optimization recommendations.
    7. Security Posture: Includes security-related features to enhance project compliance and protection.

  3. Once the project is approved by the admin, it enters the provisioning state, indicating that the project is in the process of being created. During this time, it will be labeled with an "Initialising" tag. The provisioning typically takes 25–30 minutes, and the project will remain in the Initialising state until the setup is complete. Project details

  4. Once the project is successfully created, it will be displayed with a tag "Active". Project details

  5. In case you want to open this project on the GCP console, navigate to GCP via the "Open GCP Project" link below the project name.

Navigating Using Page Path Links

Use the path link at the top of the page to quickly navigate between different levels of your project hierarchy. Simply click on any link (e.g., My Projects/Folder Name/Project Name) to jump to that specific section.

Navigation

Let us now talk about the different ways of accessing your GCP projects that are provisioned through the AI Innovation Platform, where one of them is the hyperlink present below the project name, as specified above, that will redirect you to the GCP console page of that project.

Access GCP Project Using Google Cloud SDK

Pre-requisites

  1. Install Google Cloud SDK: If the SDK is not installed, download and install it from here ⧉.
  2. Verify gCloud SDK Installation: Open Terminal (Mac/Linux) or Command Prompt (Windows).

  3. Verify the gcloud SDK version. Minimum Version: 485.0.0 or later: 

    gcloud --version or gcloud version

    If the version is older, update it using: 

    gcloud components update

Steps to access your GCP project

  1. You can create the login config by running the below command:

    gcloud iam workforce-pools create-login-config \
    locations/global/workforcePools/aiip-identity-management-prod/providers/aiip-provider-prod \
    --output-file=login.json

    The file contains the endpoints used by the gcloud CLI to enable the browser-based authentication flow and set the audience to the IdP that was configured in the workforce identity pool provider. The file doesn't contain confidential information.

    {
    "universe_domain": "googleapis.com",
    "type": "external_account_authorized_user_login_config",
    "audience": "//iam.googleapis.com/locations/global/workforcePools/aiip-identity-management-prod/providers/aiip-provider-prod",
    "auth_url": "https://auth.cloud.google/authorize",
    "token_url": "https://sts.googleapis.com/v1/oauthtoken",
    "token_info_url": "https://sts.googleapis.com/v1/introspect"
}

    Note

    This configuration file is required for logging into SDK using your identity provider. Your session will be valid for around "8 hrs" by default

  2. Run the following command

    gcloud auth login --no-launch-browser --login-config=login.json

    Open the signin link prompted and login with your access. Ensure you open the link in same browser where UI interface is authenticated.

  3. Open the above authorization link in your device Browser. Login via Google Provider.

    The above link will open the Federated login and give an authorization token which you need to enter here.

  4. Paste the token and verify your credentials.
    Your account will be in the below naming convention:

    principal://iam.googleapis.com/locations/global/workforcePools/\<WorkforcePool Name\> /subject/\<Your Email\>

    Run below command to verify the active user.

    gcloud auth list –filter=status:ACTIVE

  5. Configure gcloud SDK.
    Run the below commands to setup your cloud SDK

    gcloud config set project PROJECT_ID
gcloud config set compute/region REGION
gcloud config set compute/zone ZONE

  6. SSH into compute VM.
    Run the below SSH command to SSH into the instance: 

    gcloud beta compute ssh \<USERNAME\>@\<INSTANCE_NAME\> \--project \<PROJECT_ID\>

Note

Points to remember:

  • For JupyterHub service, username is calculated by replacing all special character by "_". E.g: If your email is "firstname.lastname@domain.com" then your username is "firstname_lastname_domain_com"
  • For compute instances, username is calculated using email.split['@'][0]. E.g: If your email is "firstname.lastname@domain.com" then your username is "firstname.lastname"
  • Username in ssh command follows all rules defined by GCP.

Note

Data Security Guidelines:

  • "Do not store your data outside of the project resources created." This includes sharing them online, on personal devices, or through any other means.
  • By using this platform, you agree to be responsible for the security of your data and to comply with these guidelines.

If you have any questions or concerns about data security, please contact our support team here ⧉.

1. Connect via VS Code

Follow these steps:

  1. Ensure VS Code IDE is installed on your device to proceed with this setup.

  2. SSH into the instance using gcloud command for allowing the GCP APIs to auto generate the SSH Keys which will be used as Identity file to connect from VS Code.

    Below are the files auto-generated by the above command in \~/.ssh/config/

  3. Start IAP tunnel for the instance to be connected to VS Code IDE.

  4. Install Remote SSH VS Code plugin

  5. Update the SSH configurations in \~/.ssh/config file and add the below. 

    Host localhost
  HostName localhost
  Port 8080
  User <ADD_USER_NAME_HERE>
  IdentityFile ~/.ssh/google_compute_engine

Note

Data Security Guidelines:

  • "Do not store your data outside of the project resources created." This includes sharing them online, on personal devices, or through any other means.
  • By using this platform, you agree to be responsible for the security of your data and to comply with these guidelines.

If you have any questions or concerns about data security, please contact our support team here ⧉.

2. Browser Based SSH

GCP offers browser based SSH functionality. Click here ⧉ for more details.

3. Use Cloud Workstations

Cloud workstations are used as an alternative to cloud shell. It provides a browser based IDE for developers.

The Cloud workstation consists of 3 stages:

This service is available in the service catalogue of the platform. Click here for more details.

4. Desktop Access

a. Remote Desktop Connection (Windows Users)

To access your GCP projects through remote desktop, you can refer to this section. With this, you will understand how to connect to Windows instances on GCP cloud. Since you are working with the secure environment, the instances would not be associated with external/public IPs, hence you need to open a secure tunnel using IAP proxy offered by GCP to securely access the instances.

Follow these steps:

1. Start IAP Tunnel
    ```
    gcloud compute start-iap-tunnel <INSTANCE_NAME> <INSTANCE_PORT> --local-host-port=localhost:<LOCAL_PORT> --project <PROJECT_NAME>
    ```
2. Login using your credentials from the Remote Desktop

    ![](images/image1112.png)
    ![](images/image1113.png)

The Windows Desktop will open post successful login.

b. IAP Desktop (Windows Users)

IAP desktop is a remote desktop and SSH client that lets you connect to your Google Cloud VM instances from anywhere. You need to make sure to download version 2.41 or later versions for using workforce Identity providers from here ⧉ and then follow the following steps

Ref: IAP Release Documentation ⧉

Note

Data Security Guidelines:

  • "Do not store your data outside of the project resources created." This includes sharing them online, on personal devices, or through any other means.
  • By using this platform, you agree to be responsible for the security of your data and to comply with these guidelines.

If you have any questions or concerns about data security, please contact our support team here ⧉.

c. Windows App (Mac Users)

  1. Install Windows App on Mac

  2. Connect to the Windows VM

    • If it's your first time using Windows App, navigate through the tour to learn more about Windows App, then select Done, or select Skip. Mac 1
    • Windows App opens on the Devices tab. Select the plus (+) icon, then select Add PC. Mac 2
    • In the dialog box that appears, for PC Name, enter the hostname as localhost. Mac 3
    • Navigate to the User account and select "Add User Account".
      • Go to My Projects, choose your project, and click on the "GCP Link". UI 1
      • In the search bar, type "VM Instance" to locate the Slicer VM. gcp 1
      • Click the dropdown icon under "Connect" and select Set Windows Password. gcp 2
      • Enter or update the Username, then click "Set". gcp 3
      • A Windows password will be generated – copy and store it securely. gcp 4
    • Click "Add"
    • Your remote PC is added to the Devices tab. Mac 4
    • On the Devices tab, double-click the remote PC to connect.

  3. Accept Certificate Warning & Login

    • If you see a certificate warning, click "Continue".

    • You should now have access to your Windows VM.

5. Common Errors

Refresh token has expired:

In this scenario, your tokens have expired and you are required to login to cloud SDK again. As per security best practices, the tokens generated for users are expired in a defined time interval.

Public key denied while connecting to VS Code:

In case you experience public key denied from VS Code IDE but are able to SSH into the instance using the gcloud command, you need to remove old keys from .ssh folder generated and perform a fresh SSH into the instance to generate new keys and try connecting again.