Pilih preferensi cookie Anda

Kami menggunakan cookie penting serta alat serupa yang diperlukan untuk menyediakan situs dan layanan. Kami menggunakan cookie performa untuk mengumpulkan statistik anonim sehingga kami dapat memahami cara pelanggan menggunakan situs dan melakukan perbaikan. Cookie penting tidak dapat dinonaktifkan, tetapi Anda dapat mengklik “Kustom” atau “Tolak” untuk menolak cookie performa.

Jika Anda setuju, AWS dan pihak ketiga yang disetujui juga akan menggunakan cookie untuk menyediakan fitur situs yang berguna, mengingat preferensi Anda, dan menampilkan konten yang relevan, termasuk iklan yang relevan. Untuk menerima atau menolak semua cookie yang tidak penting, klik “Terima” atau “Tolak”. Untuk membuat pilihan yang lebih detail, klik “Kustomisasi”.

Connecting to Amazon Q Developer in chat applications with interface VPC endpoints

Mode fokus
Connecting to Amazon Q Developer in chat applications with interface VPC endpoints - Amazon Q Developer in chat applications
Halaman ini belum diterjemahkan ke dalam bahasa Anda. Minta terjemahan

AWS Chatbot is now Amazon Q Developer. Learn more

AWS Chatbot is now Amazon Q Developer. Learn more

You can use AWS PrivateLink to create a private connection between your virtual private cloud (VPC) and Amazon Q Developer so that you can access the service as if it were in your own VPC. This doesn't require the use an internet gateway, network address translation (NAT) device, virtual private network (VPN) connection, or AWS Direct Connect connection. You establish this private connection by creating an interface endpoint that is powered by AWS PrivateLink. An interface endpoint is an elastic network interface with a private IP address that serves as an entry point for traffic destined to a supported AWS service. The endpoint provides reliable and scalable connectivity to Amazon Q Developer, without requiring an internet gateway, NAT instance, or VPN connection. Instances in your VPC don't need public IP addresses to access Amazon Q Developer. For more information, see Amazon Virtual Private Cloud and Interface VPC Endpoints (AWS PrivateLink).

Creating an interface VPC endpoint for Amazon Q Developer

You can create a VPC endpoint for Amazon Q Developer using the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see Creating an interface Endpoint in the Amazon VPC User Guide.

Create a VPC endpoint for Amazon Q Developer using one of the following service names:

  • com.amazonaws.us-east-2.chatbot

  • com.amazonaws.us-west-2.chatbot

  • com.amazonaws.eu-west-1.chatbot

  • com.amazonaws.ap-southeast-1.chatbot

If you enable private doman name system (DNS) for the endpoint, you can make API requests to Amazon Q Developer using its default DNS name. For example, chatbot.us-east-2.amazonaws.com. For more information, see Accessing a service through an interface endpoint in the Amazon VPC User Guide.

Creating a VPC endpoint policy for Amazon Q Developer

You can attach an endpoint policy to your VPC endpoint that controls access to Amazon Q Developer. The policy specifies the following information:

  • The principal that can perform actions

  • The actions that can be performed

  • The resources on which actions can be performed

For more information, see Controlling access to services with VPC endpoints in the Amazon VPC User Guide.

Example: VPC endpoint policy for Amazon Q Developer actions

The following endpoint policy grants access to the listed Amazon Q Developer actions for all principals on all resources.

{ "Statement":[ { "Principal":"*", "Effect":"Allow", "Action":[ "chatbot:CreateSlackChannelConfiguration", "chatbot:DescribeSlackChannelConfigurations", "chatbot:UpdateSlackChannelConfiguration" ], "Resource":"*" } ] }
PrivasiSyarat situsPreferensi cookie
© 2025, Amazon Web Services, Inc. atau afiliasinya. Semua hak dilindungi undang-undang.