AWS chatbot documentation change
Summary
Updated service name references from 'Amazon Q Developer in chat channels' to 'Amazon Q Developer in chat applications' throughout the document
Security assessment
The changes are purely cosmetic renaming of service terminology without altering security-related content. The documentation continues to describe CloudTrail logging functionality without introducing new security features or addressing vulnerabilities.
Diff
diff --git a/chatbot/latest/adminguide/logging-using-cloudtrail.md b/chatbot/latest/adminguide/logging-using-cloudtrail.md index 47c0a80fe..8a281f23e 100644 --- a//chatbot/latest/adminguide/logging-using-cloudtrail.md +++ b//chatbot/latest/adminguide/logging-using-cloudtrail.md @@ -5 +5 @@ -Logging Amazon Q Developer in chat channels API information in CloudTrailLogging other AWS API information in CloudTrailExample: Amazon Q Developer in chat channels log file entries +Logging Amazon Q Developer in chat applications API information in CloudTrailLogging other AWS API information in CloudTrailExample: Amazon Q Developer in chat applications log file entries @@ -15 +15 @@ AWS Chatbot has integrated with Amazon Q Developer. [Learn more](./service-renam -Amazon Q Developer in chat channels integrates events with AWS CloudTrail, a service that provides a record of actions taken by a user, role, or an AWS service in Amazon Q Developer in chat channels. CloudTrail captures API calls for Amazon Q Developer in chat channels as events. The calls captured include calls from the Amazon Q Developer in chat channels console and code calls to the Amazon Q Developer in chat channels API operations. If you create a trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for Amazon Q Developer in chat channels. If you don't configure a trail, you can still view the most recent events in the CloudTrail console in **Event history**. Using the information collected by CloudTrail, you can determine the request that was made to Amazon Q Developer in chat channels, the IP address from which the request was made, who made the request, when it was made, and additional details. For more information, see [Viewing Events with CloudTrail Event History](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/view-cloudtrail-events.html). +Amazon Q Developer in chat applications integrates events with AWS CloudTrail, a service that provides a record of actions taken by a user, role, or an AWS service in Amazon Q Developer in chat applications. CloudTrail captures API calls for Amazon Q Developer in chat applications as events. The calls captured include calls from the Amazon Q Developer in chat applications console and code calls to the Amazon Q Developer in chat applications API operations. If you create a trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for Amazon Q Developer in chat applications. If you don't configure a trail, you can still view the most recent events in the CloudTrail console in **Event history**. Using the information collected by CloudTrail, you can determine the request that was made to Amazon Q Developer in chat applications, the IP address from which the request was made, who made the request, when it was made, and additional details. For more information, see [Viewing Events with CloudTrail Event History](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/view-cloudtrail-events.html). @@ -19 +19 @@ To learn more about CloudTrail, including how to configure and enable it, see th -When you create a _trail_ , you can enable continuous delivery of Amazon Q Developer in chat channels events to an Amazon S3 bucket that you specify. The trail logs events from all Regions in the AWS partition for that service and delivers the log files to that Amazon S3 bucket. You can configure other AWS services to further analyze and act upon the event data collected in CloudTrail logs. For more information, see the following topics in the _AWS CloudTrail User Guide_ : +When you create a _trail_ , you can enable continuous delivery of Amazon Q Developer in chat applications events to an Amazon S3 bucket that you specify. The trail logs events from all Regions in the AWS partition for that service and delivers the log files to that Amazon S3 bucket. You can configure other AWS services to further analyze and act upon the event data collected in CloudTrail logs. For more information, see the following topics in the _AWS CloudTrail User Guide_ : @@ -32 +32 @@ When you create a _trail_ , you can enable continuous delivery of Amazon Q Devel -## Logging Amazon Q Developer in chat channels API information in CloudTrail +## Logging Amazon Q Developer in chat applications API information in CloudTrail @@ -49 +49 @@ For more information, see the [CloudTrail userIdentity Element](https://docs.aws -When you use commands in Amazon Q Developer in chat channels that call APIs from other AWS services, those APIs are logged in CloudTrail as well. +When you use commands in Amazon Q Developer in chat applications that call APIs from other AWS services, those APIs are logged in CloudTrail as well. @@ -51 +51 @@ When you use commands in Amazon Q Developer in chat channels that call APIs from -When you run a command that involves another AWS service, Amazon Q Developer in chat channels assumes an IAM role in your account to invoke AWS APIs on your behalf. These APIs appear in your CloudTrail events, and they are associated with the role that was configured for your Amazon Q Developer in chat channels configuration with a session name that includes **chatbot** , such as **chatbot-session**. +When you run a command that involves another AWS service, Amazon Q Developer in chat applications assumes an IAM role in your account to invoke AWS APIs on your behalf. These APIs appear in your CloudTrail events, and they are associated with the role that was configured for your Amazon Q Developer in chat applications configuration with a session name that includes **chatbot** , such as **chatbot-session**. @@ -53 +53 @@ When you run a command that involves another AWS service, Amazon Q Developer in -Because Amazon Q Developer in chat channels is a global service, it may process your events in a different AWS Region. An API call is logged in the region where the resource behind that API call exists. For example, if you run a `lambda list-functions` command in Amazon Q Developer in chat channels, CloudTrail will log two APIs: **AssumeRole** and **ListFunctions**. The **AssumeRole** call is logged in the Region Amazon Q Developer in chat channels processed it in, and the **ListFunctions** call is logged in the Region the function exists in. +Because Amazon Q Developer in chat applications is a global service, it may process your events in a different AWS Region. An API call is logged in the region where the resource behind that API call exists. For example, if you run a `lambda list-functions` command in Amazon Q Developer in chat applications, CloudTrail will log two APIs: **AssumeRole** and **ListFunctions**. The **AssumeRole** call is logged in the Region Amazon Q Developer in chat applications processed it in, and the **ListFunctions** call is logged in the Region the function exists in. @@ -55 +55 @@ Because Amazon Q Developer in chat channels is a global service, it may process -## Example: Amazon Q Developer in chat channels log file entries +## Example: Amazon Q Developer in chat applications log file entries @@ -59 +59 @@ CloudTrail log files contain one or more log entries. An event represents a sing -The following example shows a CloudTrail log entry for the Amazon Q Developer in chat channels `DescribeSlackChannels` action. +The following example shows a CloudTrail log entry for the Amazon Q Developer in chat applications `DescribeSlackChannels` action.