Skip to main content

Kiro cloud sessions now reach private networks

RY

Rydel Dcosta

Engineering

MI

Mike Landi

Engineering

Kiro cloud sessions can now attach to a VPC that your admin configures. Until now, a cloud session could reach the public internet and Kiro’s own services, but nothing inside your private network, so an agent could not install from an internal package mirror, run integration tests against a database with no public address, or call a build server that only answers from inside your perimeter. Starting today, an admin registers a VPC once, every cloud session created afterward joins it automatically, and your own network decides what those sessions can reach. You also control the agent’s internet access because everything except Kiro’s own traffic leaves through your VPC. VPC connections are available on Enterprise plans for IAM Identity Center profiles.

This launch ships alongside Kiro remote workspaces, which lets developers open cloud sessions, dev containers, and their own machines directly from Kiro IDE. Remote workspaces decides where the work runs, and a VPC connection decides what that work can reach.

Loading image...The VPC connections page in Kiro settings, titled 'Connections (1)', with a note that connections can't be edited and a Delete button and a Connect a VPC button at the top right. A table with columns Name, Status, Account, VPC, Region, and Last updated lists one connection named prod-shared with a green Active status, 'This account' as the account, a VPC ID, and the region us-east-1.

Why cloud sessions needed a way into your network

Enterprise code rarely builds from public sources alone. Dependencies come from an internal registry, tests run against staging services and data stores that have no public address, and some of the systems an agent needs sit behind Transit Gateway, VPN, or Direct Connect in an on-premises data center. Without a path in, teams kept this work on local machines or opened holes in their perimeter to make the cloud reachable, and neither is ideal. A VPC connection gives the cloud session a seat inside your network, so the agent works against your real development environment and your existing network controls keep applying.

Picture an agent asked to add a dependency and run the service’s tests. In a cloud session without a VPC connection, the install times out because the package lives on an internal Artifactory that only answers inside your network. With a VPC connection, the same command resolves the internal hostname through your DNS, installs from the mirror, and the agent moves on to the integration tests against your staging database.

What a connected session can reach

A connected session reaches anything your VPC can route to, by IP address or internal hostname. That includes private package registries and artifact stores such as Artifactory and Nexus, internal APIs and services, databases and data stores, and on-premises systems reachable through Transit Gateway, peering, VPN, or Direct Connect. Your NAT, firewall, Flow Logs, and network ACLs apply to the session’s traffic because from your network’s point of view the session is another host in your subnet. Source control integrations such as GitHub and GitLab configured in Kiro Web keep working through the integrations you have already connected.

How it works

When a session starts, Kiro attaches a network interface in your VPC and makes it the session’s default route. Private hostnames resolve through your DNS and connect the way they would from any machine on your network. Kiro’s own traffic stays on Kiro’s network. That covers the model, the control plane, and telemetry. To do its work, the agent sends the model your prompts and the context it gathers in the session, such as file contents and command output, and that traffic never passes through your VPC. Anything that is not a Kiro service leaves through your VPC, so your NAT, firewall, and data loss controls decide what gets out.

Setting it up

An admin sets up a connection once under Kiro Settings > Manage VPC connections, using a five-step wizard.

First, the admin gives Kiro a service role in this account. The console can create one whose trust policy lets Kiro assume it only on behalf of this profile, using source account and source ARN conditions, or the admin can choose an existing role.

Loading image...The Service role step of the Connect a VPC wizard. Two options under IAM role: 'Create a new service role', selected and marked Recommended, and 'Use an existing role'. Below are a generated role name beginning KiroVpcConnection, a Create role button, and an expanded 'View the service role's policies' section showing a trust policy JSON that lets the q.amazonaws.com service assume the role with aws:SourceAccount and aws:SourceArn conditions, followed by a Permissions section naming the AWS managed KiroVpcConnectionPolicy.

Next, the admin says where the VPC lives. For a VPC in another account, such as a shared networking account, the admin adds a role there that trusts the first one.

Loading image...The VPC account step of the Connect a VPC wizard, with the five steps listed on the left and step 2 highlighted. The question 'Where is the VPC?' shows the chosen service role ARN and two options, 'This account', selected, and 'Another account'. A green message reads 'Kiro can use this role. Found 2 VPCs in us-east-1.' Cancel, Previous, and Next buttons sit at the bottom right.

Then the admin picks the VPC and the subnets Kiro may use. The wizard shows each subnet’s zone and free IP addresses and estimates how many sessions can run at once.

Loading image...The VPC and subnets step of the Connect a VPC wizard. A VPC dropdown shows one selected VPC. Below, 'Subnets Kiro may use (3/4)' lists four subnets with their zone IDs and free IP addresses; the first three are checked and the fourth is unchecked. A summary underneath reads 'Up to 752' sandboxes that can run at once and lists the zones covered.

The admin chooses one to five security groups they own in the VPC. Kiro never creates or changes security groups, so the groups you choose define what sessions can reach.

Loading image...The Security groups step of the Connect a VPC wizard. A blue notice says security groups decide what sandboxes can reach, and that Kiro never creates or changes them. A table 'Security groups (1/5)' lists two groups: the VPC's default security group, unchecked and flagged with a red 'The VPC's default security group can't be used' check message, and a group named kiro-sandboxes, checked.

Finally, Kiro checks the connection and creates it only when every check passes, listing each problem with its fix. The connection takes effect once the admin makes it the default in Controls. The full list of checks and warnings is in the VPC connections docs.

What developers see

Developers never enter network details. In this release, every new cloud session connects to the admin’s default connection, and developers see it as a read-only card in Kiro Web’s sandbox settings, for example, Connected to prod-shared, with the VPC ID, and region. The card says it applies to new sessions, and a session’s own page shows the connection that session actually has, which can differ from the current default after an admin edit.

Loading image...The Sandbox page in Kiro Web settings. Under Network configuration, the access level reads 'Connections only', set by your VPC connection, with 'Repository access only' shown as overridden. A 'VPC connectivity' section says your Kiro admin manages this connection and that new sandboxes will connect to prod-shared, with its VPC ID and the region us-east-1. Environment variables and Secrets sections with add buttons follow.
Loading image...The new session screen in Kiro Web with the network access menu open. The top option, highlighted in purple, reads 'VPC connections only - prod-shared'. The other options, 'Open internet', 'Common dependencies', and 'Repository access only', are dimmed.

The same information is shown in session info in the IDE and CLI.

Loading image...Kiro CLI V3 welcome screen in a terminal showing a cloud session. Status lines confirm the connection to kiro.dev and that a cloud session was created. At the bottom right, a red outline highlights the line 'VPC prod-shared', followed by the VPC ID and the region us-east-1.

Security and control

The role Kiro assumes can only create, tag, and delete the network interfaces that Kiro tags in the VPC you named, plus read-only describe calls. Kiro holds no long-lived credentials in your account, and each temporary session lasts at most an hour. Every action appears in your CloudTrail, including the role assumption, the network interface creation and deletion, and the read-only calls used for validation. The security groups are yours, so you can tighten egress to specific destinations or widen it to peered and on-premises ranges at any time, and rule changes apply immediately, including to running sessions.

Things to know before you roll it out

The VPC must be in the same region as the cloud session. A session can attach to one customer VPC, and it needs a subnet in each availability zone Kiro uses, so a session in a zone with no subnet cannot attach. Each connected session takes one IP address in your subnet, so size subnets for the number of concurrent sessions you expect, and keep customer CIDRs from overlapping 100.124.0.0/16, 172.17.0.0/16, and 169.254.0.0/16. The network is fixed when a session starts, so an admin edit applies to new sessions only, and a resumed session gets a new interface in the same VPC. If the connection was deleted, the session will not resume.

Common questions

Does it work with my on-premises network?

Yes, for anything your VPC routes to, including Transit Gateway, peering, VPN, and Direct Connect.

Does a connected session start slower?

Yes. Kiro creates a network interface in your subnet when the session starts, so a connected session takes longer to start than a regular one.

Does it work in the IDE and CLI?

Yes. VPC settings are used for cloud sessions started from the IDE, CLI, and Web.

Does it work with a VPC in another AWS account?

Yes. The admin supplies a role ARN in the other account.

Can I use more than one VPC?

An admin can register multiple connections, and one is the default for new sessions. A session attaches to one VPC, and developers cannot pick between connections in this release.

Is this available on every plan?

VPC connections are available only on Enterprise plans for IAM Identity Center profiles today.

Update to Kiro IDE 1.4.236 or later, or Kiro CLI 3.5.0 or later, to see your VPC connection in session info. Admins can set up a connection by following the VPC connections docs.