I tried creating a remote connection environment for Kiro IDE in Amazon SageMaker Unified Studio
This page has been translated by machine translation. View original
Introduction
Have you ever wanted to connect to a remote server while using Kiro IDE on a regular basis?
In VS Code, remote connection via the Remote SSH extension is the standard approach, but in Kiro IDE there is no reliable Remote SSH extension, making remote server connections a challenging issue.
Given these constraints, Amazon SageMaker Unified Studio appears to support remote connections from Kiro IDE, so I decided to give it a try.
What is Amazon SageMaker Unified Studio?
Amazon SageMaker Unified Studio is an integrated development environment that allows centralized management of data, analytics, and AI/ML development.
Resources can be managed per project, and development environments (Spaces) such as code editors and notebooks can be hosted in the cloud.
You might brace yourself when you hear SageMaker, thinking it's something complex related to machine learning, but this time we're simply creating a code editor as a remote environment, so there are no complicated operations involved.
Let's give it a try.
Creating a Domain
As a prerequisite, since IAM Identity Center is not available in this environment, authentication will be done using IAM.
IAM Identity Center-based authentication is also available as an authentication method, so if you are using IAM Identity Center, please also consider Identity Center based domains.
First, create a domain in SageMaker Unified Studio.
From the SageMaker console, go to Domains > Set up IAM-based domain > click "Set up"
Since there are no special requirements this time, simply click "Set up" to complete.
Creating a Space
Once the domain is created, you will be taken to the SageMaker Unified Studio screen, so click "Open".
Open Spaces from the left menu.
You can see the Kiro icon in the section for connecting from a local IDE, which is promising!
Click "Editor for VS Code" to proceed to the space creation screen.
Creating a Space
Set the space name and IDE type.
Select "Code Editor" for the IDE.
Next, select ml.t3.large for the instance.
There is a smaller instance type available, but since enabling remote access from local requires 8GB of memory, we are selecting ml.t3.large as the minimum instance that meets that requirement.
Next, check the remote access checkbox to allow access from your local Kiro.
Finally, use the default idle timeout of 1 hour.
Please enter an appropriate time here.
It's a great feature for preventing you from forgetting to stop the remote server.
Connecting Remotely from Kiro IDE
Once the space is running, connect from Kiro IDE.
Connection Procedure
Returning to the space list, the created space will be displayed.
Click the Kiro icon that appears in the space's dropdown menu.
The local Kiro IDE will launch and the SageMaker remote connection screen will open.
After a short wait, you will be taken to the sign-in method selection screen.
Please authenticate with Kiro according to your own environment.
Once authentication is complete, you will be automatically connected to the remote space.
The connection is complete when a new window opens and the files on the space are displayed as a remote workspace.
Starting and Stopping the Remote Server from Kiro
Once you have created a space, you can also start the remote server from Kiro.
Click the AWS icon from Kiro's left menu, and the created space will be displayed in the SAGEMAKER UNIFIED STUDIO menu.
At this point, the space is stopped.
Double-clicking the space you want to start will display (Starting) to the right of the space name, and after a short wait, a new Kiro window for remote connection will open just as before.
The subsequent steps are the same.
To stop it, a stop button will appear on the right side of the space, and clicking it will stop it.
It's convenient to be able to operate directly from Kiro, since logging into AWS every time to start the remote server would be cumbersome.
Conclusion
I created an environment for connecting remotely from Kiro IDE using Amazon SageMaker Unified Studio.
It's great that you can connect from your local Kiro simply by enabling remote access when creating a space.
In addition, the idle timeout feature that automatically reduces billing when unused is also a welcome feature for a remote server.