AWS chatbot documentation change
Summary
Updated documentation to specify 'Amazon Q Developer in chat channels' in VPC endpoint configuration instructions and policy examples
Security assessment
The changes clarify the service context (chat channels) but do not introduce new security controls or address vulnerabilities. The updates focus on branding consistency and specificity rather than security mechanisms.
Diff
diff --git a/chatbot/latest/adminguide/vpc.md b/chatbot/latest/adminguide/vpc.md index b9e7a548e..c5e3bab75 100644 --- a//chatbot/latest/adminguide/vpc.md +++ b//chatbot/latest/adminguide/vpc.md @@ -5 +5 @@ -Creating an interface VPC endpoint for Amazon Q DeveloperCreating a VPC endpoint policy for Amazon Q Developer +Creating an interface VPC endpoint for Amazon Q Developer in chat channelsCreating a VPC endpoint policy for Amazon Q Developer in chat channels @@ -11 +11 @@ AWS Chatbot is now Amazon Q Developer. [Learn more](./service-rename.html) -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](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html) and [Interface VPC Endpoints (AWS PrivateLink)](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint). +You can use AWS PrivateLink to create a private connection between your virtual private cloud (VPC) and Amazon Q Developer in chat channels so that you can access the service as if it were in your own VPC. This doesn't require the use of 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 in chat channels, 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 in chat channels. For more information, see [Amazon Virtual Private Cloud](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html) and [Interface VPC Endpoints (AWS PrivateLink)](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint). @@ -15 +15 @@ You can use AWS PrivateLink to create a private connection between your virtual - * Creating an interface VPC endpoint for Amazon Q Developer + * Creating an interface VPC endpoint for Amazon Q Developer in chat channels @@ -17 +17 @@ You can use AWS PrivateLink to create a private connection between your virtual - * Creating a VPC endpoint policy for Amazon Q Developer + * Creating a VPC endpoint policy for Amazon Q Developer in chat channels @@ -22 +22 @@ You can use AWS PrivateLink to create a private connection between your virtual -## Creating an interface VPC endpoint for Amazon Q Developer +## Creating an interface VPC endpoint for Amazon Q Developer in chat channels @@ -24 +24 @@ You can use AWS PrivateLink to create a private connection between your virtual -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](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint) in the _Amazon VPC User Guide_. +You can create a VPC endpoint for Amazon Q Developer in chat channels using the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Creating an interface Endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint) in the _Amazon VPC User Guide_. @@ -26 +26 @@ You can create a VPC endpoint for Amazon Q Developer using the Amazon VPC consol -Create a VPC endpoint for Amazon Q Developer using one of the following service names: +Create a VPC endpoint for Amazon Q Developer in chat channels using one of the following service names: @@ -39 +39 @@ Create a VPC endpoint for Amazon Q Developer using one of the following service -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](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#access-service-though-endpoint) in the _Amazon VPC User Guide_. +If you enable private domain name system (DNS) for the endpoint, you can make API requests to Amazon Q Developer in chat channels using its default DNS name. For example, `chatbot.us-east-2.amazonaws.com`. For more information, see [Accessing a service through an interface endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#access-service-though-endpoint) in the _Amazon VPC User Guide_. @@ -41 +41 @@ If you enable private doman name system (DNS) for the endpoint, you can make API -## Creating a VPC endpoint policy for Amazon Q Developer +## Creating a VPC endpoint policy for Amazon Q Developer in chat channels @@ -43 +43 @@ If you enable private doman name system (DNS) for the endpoint, you can make API -You can attach an endpoint policy to your VPC endpoint that controls access to Amazon Q Developer. The policy specifies the following information: +You can attach an endpoint policy to your VPC endpoint that controls access to Amazon Q Developer in chat channels. The policy specifies the following information: @@ -56 +56 @@ For more information, see [Controlling access to services with VPC endpoints](ht -### Example: VPC endpoint policy for Amazon Q Developer actions +### Example: VPC endpoint policy for Amazon Q Developer in chat channels actions @@ -58 +58 @@ For more information, see [Controlling access to services with VPC endpoints](ht -The following endpoint policy grants access to the listed Amazon Q Developer actions for all principals on all resources. +The following endpoint policy grants access to the listed Amazon Q Developer in chat channels actions for all principals on all resources.