Cookie の設定を選択する

当社は、当社のサイトおよびサービスを提供するために必要な必須 Cookie および類似のツールを使用しています。当社は、パフォーマンス Cookie を使用して匿名の統計情報を収集することで、お客様が当社のサイトをどのように利用しているかを把握し、改善に役立てています。必須 Cookie は無効化できませんが、[カスタマイズ] または [拒否] をクリックしてパフォーマンス Cookie を拒否することはできます。

お客様が同意した場合、AWS および承認された第三者は、Cookie を使用して便利なサイト機能を提供したり、お客様の選択を記憶したり、関連する広告を含む関連コンテンツを表示したりします。すべての必須ではない Cookie を受け入れるか拒否するには、[受け入れる] または [拒否] をクリックしてください。より詳細な選択を行うには、[カスタマイズ] をクリックしてください。

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":"*" } ] }
プライバシーサイト規約Cookie の設定
© 2025, Amazon Web Services, Inc. or its affiliates.All rights reserved.