쿠키 기본 설정 선택

당사는 사이트와 서비스를 제공하는 데 필요한 필수 쿠키 및 유사한 도구를 사용합니다. 고객이 사이트를 어떻게 사용하는지 파악하고 개선할 수 있도록 성능 쿠키를 사용해 익명의 통계를 수집합니다. 필수 쿠키는 비활성화할 수 없지만 '사용자 지정' 또는 ‘거부’를 클릭하여 성능 쿠키를 거부할 수 있습니다.

사용자가 동의하는 경우 AWS와 승인된 제3자도 쿠키를 사용하여 유용한 사이트 기능을 제공하고, 사용자의 기본 설정을 기억하고, 관련 광고를 비롯한 관련 콘텐츠를 표시합니다. 필수가 아닌 모든 쿠키를 수락하거나 거부하려면 ‘수락’ 또는 ‘거부’를 클릭하세요. 더 자세한 내용을 선택하려면 ‘사용자 정의’를 클릭하세요.

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

포커스 모드
Connecting to Amazon Q Developer in chat applications with interface VPC endpoints - Amazon Q Developer in chat applications
이 페이지는 귀하의 언어로 번역되지 않았습니다. 번역 요청

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":"*" } ] }
프라이버시사이트 이용 약관쿠키 기본 설정
© 2025, Amazon Web Services, Inc. 또는 계열사. All rights reserved.