AWS chatbot documentation change
Summary
Updated terminology from 'chat channels' to 'chat applications' throughout the document, including references to Amazon Q Developer and CLI command limitations
Security assessment
Changes are purely terminological updates (channels→applications) with no evidence of addressing security vulnerabilities or introducing new security controls. The existing security restriction about IAM/STS/KMS command limitations remains unchanged except for terminology.
Diff
diff --git a/chatbot/latest/adminguide/intro-to-the-aws-cli-in-slack.md b/chatbot/latest/adminguide/intro-to-the-aws-cli-in-slack.md index 25431089a..59e4c2b86 100644 --- a//chatbot/latest/adminguide/intro-to-the-aws-cli-in-slack.md +++ b//chatbot/latest/adminguide/intro-to-the-aws-cli-in-slack.md @@ -7 +7 @@ AWS Chatbot is now Amazon Q Developer. [Learn more](./service-rename.html) -# AWS CLI command syntax in Amazon Q Developer in chat channels +# AWS CLI command syntax in Amazon Q Developer in chat applications @@ -9 +9 @@ AWS Chatbot is now Amazon Q Developer. [Learn more](./service-rename.html) -After you set up the Amazon Q Developer in chat channels, you run commands with the following prefix: +After you set up the Amazon Q Developer in chat applications, you run commands with the following prefix: @@ -15 +15 @@ After you set up the Amazon Q Developer in chat channels, you run commands with -If you are using Slack and AWS is not listed as a valid member of the channel, you need to add the Amazon Q Developer in chat channels app to the Slack workspace and invite it to the channel. For more information, see the [Getting started guide for Amazon Q Developer in chat channels](./getting-started.html). +If you are using Slack and AWS is not listed as a valid member of the channel, you need to add the Amazon Q Developer in chat applications app to the Slack workspace and invite it to the channel. For more information, see the [Getting started guide for Amazon Q Developer in chat applications](./getting-started.html). @@ -21 +21 @@ Instead of entering `@Amazon Q`, you can enter `@Q` and choose the autocomplete -The Amazon Q Developer in chat channels command syntax is the same as you would use in a terminal: +The Amazon Q Developer in chat applications command syntax is the same as you would use in a terminal: @@ -31 +31 @@ You can specify parameters with either a double hyphen (`--option`) or a single -AWS CLI commands run from AWS Chatbot have an execution [timeout](https://docs.aws.amazon.com/whitepapers/latest/serverless-architectures-lambda/timeout.html) of 15 seconds. If a command response is not received within 15 seconds, you receive a timeout error message. If you have longer running jobs, such as AWS Lambda functions, you should invoke them asynchronously from Amazon Q Developer in chat channels. The maximum allowable Lambda function execution timeout is 900 seconds (15 minutes). For more information about asynchronous invocation, see [Asynchronous invocation](https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html) in the _AWS Lambda Developer Guide_. +AWS CLI commands run from AWS Chatbot have an execution [timeout](https://docs.aws.amazon.com/whitepapers/latest/serverless-architectures-lambda/timeout.html) of 15 seconds. If a command response is not received within 15 seconds, you receive a timeout error message. If you have longer running jobs, such as AWS Lambda functions, you should invoke them asynchronously from Amazon Q Developer in chat applications. The maximum allowable Lambda function execution timeout is 900 seconds (15 minutes). For more information about asynchronous invocation, see [Asynchronous invocation](https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html) in the _AWS Lambda Developer Guide_. @@ -45 +45 @@ You can also use CLI commands to change you AWS resources. For example, enter th -You can enter a complete AWS CLI command with all the parameters, or you can enter the command without parameters and Amazon Q Developer in chat channels prompts you for missing parameters. +You can enter a complete AWS CLI command with all the parameters, or you can enter the command without parameters and Amazon Q Developer in chat applications prompts you for missing parameters. @@ -47 +47 @@ You can enter a complete AWS CLI command with all the parameters, or you can ent -For more information on commonly used CLI commands, see [Using CLI commands with Amazon Q Developer in chat channels - Common use cases](./common-use-cases.html). For an exhaustive list of CLI commands, see the [AWS CLI Command Reference](https://docs.aws.amazon.com/cli/latest/index.html). +For more information on commonly used CLI commands, see [Using CLI commands with Amazon Q Developer in chat applications - Common use cases](./common-use-cases.html). For an exhaustive list of CLI commands, see the [AWS CLI Command Reference](https://docs.aws.amazon.com/cli/latest/index.html). @@ -55 +55 @@ The following limitations apply to running AWS CLI commands in your chat rooms: - * You may experience some latency when invoking commands through Amazon Q Developer in chat channels. + * You may experience some latency when invoking commands through Amazon Q Developer in chat applications. @@ -57 +57 @@ The following limitations apply to running AWS CLI commands in your chat rooms: - * Regardless of their Amazon Q Developer in chat channels role permissions, users cannot run IAM, AWS Security Token Service, or AWS Key Management Service commands within chat channels. + * Regardless of their Amazon Q Developer in chat applications role permissions, users cannot run IAM, AWS Security Token Service, or AWS Key Management Service commands within chat channels. @@ -59 +59 @@ The following limitations apply to running AWS CLI commands in your chat rooms: - * Amazon S3 service commands support Linux-style command aliases such as **ls** and **cp**. Amazon Q Developer in chat channels does not support Amazon S3 command aliases for commands in Slack. + * Amazon S3 service commands support Linux-style command aliases such as **ls** and **cp**. Amazon Q Developer in chat applications does not support Amazon S3 command aliases for commands in Slack.