This documentation is a copy of the public Kiro documentation. For supplemental information that is specific to this region, such as feature and service availability, see the AWS Classified Regions User Guide. Published: October 14, 2026.
You can establish a private connection between your VPC and Kiro by creating an interface VPC endpoint. Interface endpoints are powered by
Each interface endpoint is represented by one or more
For more information, see
Before you set up an interface VPC endpoint for Kiro, ensure that you review
Kiro supports making calls to all of its API actions from your VPC, in the context of services that are configured to work with Kiro.
Before you begin any of the procedures below, ensure that you have the following:
You can create a VPC endpoint for Kiro using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see
Create a VPC endpoint for Kiro using one of the following service names:
If you enable private DNS for the endpoint, you can make API requests to Kiro using its default DNS name for the region, for example, q.us-east-1.amazonaws.com, runtime.us-east-1.kiro.dev.
The following private DNS names also resolve through the existing VPC endpoint automatically. No additional endpoints or configuration changes are required:
runtime.<region>.kiro.devmanagement.<region>.kiro.devtelemetry.<region>.kiro.devWhere <region> is us-east-1 or eu-central-1.
For more information, see
This section describes the process of using an on-premises computer to connect to Kiro through an AWS PrivateLink endpoint in your AWS VPC.
Kiro and interface endpoints (AWS PrivateLink)