|
32 | 32 | {"shape":"InternalServerException"},
|
33 | 33 | {"shape":"ConflictException"}
|
34 | 34 | ],
|
35 |
| - "documentation":"<p>Creates an <i>investigation group</i> in your account. Creating an investigation group is a one-time setup task for each Region in your account. It is a necessary task to be able to perform investigations.</p> <p>Settings in the investigation group help you centrally manage the common properties of your investigations, such as the following:</p> <ul> <li> <p>Who can access the investigations</p> </li> <li> <p>Whether investigation data is encrypted with a customer managed Key Management Service key.</p> </li> <li> <p>How long investigations and their data are retained by default.</p> </li> </ul> <p>Currently, you can have one investigation group in each Region in your account. Each investigation in a Region is a part of the investigation group in that Region</p> <p>To create an investigation group and set up Amazon Q Developer operational investigations, you must be signed in to an IAM principal that has the either the <code>AIOpsConsoleAdminPolicy</code> or the <code>AdministratorAccess</code> IAM policy attached, or to an account that has similar permissions.</p> <important> <p>You can configure CloudWatch alarms to start investigations and add events to investigations. If you create your investigation group with <code>CreateInvestigationGroup</code> and you want to enable alarms to do this, you must use <a href=\"https://docs.aws.amazon.com/operationalinvestigations/latest/AmazonQDeveloperOperationalInvestigationsAPIReference/API_PutInvestigationGroupPolicy.html\">PutInvestigationGroupPolicy</a> to create a resource policy that grants this permission to CloudWatch alarms. </p> <p>For more information about configuring CloudWatch alarms to work with Amazon Q Developer operational investigations, see </p> </important>", |
| 35 | + "documentation":"<p>Creates an <i>investigation group</i> in your account. Creating an investigation group is a one-time setup task for each Region in your account. It is a necessary task to be able to perform investigations.</p> <p>Settings in the investigation group help you centrally manage the common properties of your investigations, such as the following:</p> <ul> <li> <p>Who can access the investigations</p> </li> <li> <p>Whether investigation data is encrypted with a customer managed Key Management Service key.</p> </li> <li> <p>How long investigations and their data are retained by default.</p> </li> </ul> <p>Currently, you can have one investigation group in each Region in your account. Each investigation in a Region is a part of the investigation group in that Region</p> <p>To create an investigation group and set up CloudWatch investigations, you must be signed in to an IAM principal that has the either the <code>AIOpsConsoleAdminPolicy</code> or the <code>AdministratorAccess</code> IAM policy attached, or to an account that has similar permissions.</p> <important> <p>You can configure CloudWatch alarms to start investigations and add events to investigations. If you create your investigation group with <code>CreateInvestigationGroup</code> and you want to enable alarms to do this, you must use <a href=\"https://docs.aws.amazon.com/operationalinvestigations/latest/AmazonQDeveloperOperationalInvestigationsAPIReference/API_PutInvestigationGroupPolicy.html\">PutInvestigationGroupPolicy</a> to create a resource policy that grants this permission to CloudWatch alarms. </p> <p>For more information about configuring CloudWatch alarms to work with CloudWatch investigations, see </p> </important>", |
36 | 36 | "idempotent":true
|
37 | 37 | },
|
38 | 38 | "DeleteInvestigationGroup":{
|
|
154 | 154 | {"shape":"InternalServerException"},
|
155 | 155 | {"shape":"ConflictException"}
|
156 | 156 | ],
|
157 |
| - "documentation":"<p>Displays the tags associated with a Amazon Q Developer operational investigations resource. Currently, investigation groups support tagging.</p>" |
| 157 | + "documentation":"<p>Displays the tags associated with a CloudWatch investigations resource. Currently, investigation groups support tagging.</p>" |
158 | 158 | },
|
159 | 159 | "PutInvestigationGroupPolicy":{
|
160 | 160 | "name":"PutInvestigationGroupPolicy",
|
|
296 | 296 | "members":{
|
297 | 297 | "name":{
|
298 | 298 | "shape":"StringWithPatternAndLengthLimits",
|
299 |
| - "documentation":"<p>A name for the investigation group.</p>" |
| 299 | + "documentation":"<p>Provides a name for the investigation group.</p>" |
300 | 300 | },
|
301 | 301 | "roleArn":{
|
302 | 302 | "shape":"RoleArn",
|
303 |
| - "documentation":"<p>Specify the ARN of the IAM role that Amazon Q Developer operational investigations will use when it gathers investigation data. The permissions in this role determine which of your resources that Amazon Q Developer operational investigations will have access to during investigations.</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Security.html#Investigations-Security-Data\">How to control what data Amazon Q has access to during investigations</a>.</p>" |
| 303 | + "documentation":"<p>Specify the ARN of the IAM role that CloudWatch investigations will use when it gathers investigation data. The permissions in this role determine which of your resources that CloudWatch investigations will have access to during investigations.</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Security.html#Investigations-Security-Data\">How to control what data Amazon Q has access to during investigations</a>.</p>" |
304 | 304 | },
|
305 | 305 | "encryptionConfiguration":{
|
306 | 306 | "shape":"EncryptionConfiguration",
|
307 |
| - "documentation":"<p>Use this structure if you want to use a customer managed KMS key to encrypt your investigation data. If you omit this parameter, Amazon Q Developer operational investigations will use an Amazon Web Services key to encrypt the data. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Security.html#Investigations-KMS\">Encryption of investigation data</a>.</p>" |
| 307 | + "documentation":"<p>Use this structure if you want to use a customer managed KMS key to encrypt your investigation data. If you omit this parameter, CloudWatch investigations will use an Amazon Web Services key to encrypt the data. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Security.html#Investigations-KMS\">Encryption of investigation data</a>.</p>" |
308 | 308 | },
|
309 | 309 | "retentionInDays":{
|
310 | 310 | "shape":"Retention",
|
|
320 | 320 | },
|
321 | 321 | "chatbotNotificationChannel":{
|
322 | 322 | "shape":"ChatbotNotificationChannel",
|
323 |
| - "documentation":"<p>Use this structure to integrate Amazon Q Developer operational investigations with Amazon Q in chat applications. This structure is a string array. For the first string, specify the ARN of an Amazon SNS topic. For the array of strings, specify the ARNs of one or more Amazon Q in chat applications configurations that you want to associate with that topic. For more information about these configuration ARNs, see <a href=\"https://docs.aws.amazon.com/chatbot/latest/adminguide/getting-started.html\">Getting started with Amazon Q in chat applications</a> and <a href=\"https://docs.aws.amazon.com/service-authorization/latest/reference/list_awschatbot.html#awschatbot-resources-for-iam-policies\">Resource type defined by Amazon Web Services Chatbot</a>.</p>" |
| 323 | + "documentation":"<p>Use this structure to integrate CloudWatch investigations with Amazon Q in chat applications. This structure is a string array. For the first string, specify the ARN of an Amazon SNS topic. For the array of strings, specify the ARNs of one or more Amazon Q in chat applications configurations that you want to associate with that topic. For more information about these configuration ARNs, see <a href=\"https://docs.aws.amazon.com/chatbot/latest/adminguide/getting-started.html\">Getting started with Amazon Q in chat applications</a> and <a href=\"https://docs.aws.amazon.com/service-authorization/latest/reference/list_awschatbot.html#awschatbot-resources-for-iam-policies\">Resource type defined by Amazon Web Services Chatbot</a>.</p>" |
324 | 324 | },
|
325 | 325 | "isCloudTrailEventHistoryEnabled":{
|
326 | 326 | "shape":"Boolean",
|
327 |
| - "documentation":"<p>Specify <code>true</code> to enable Amazon Q Developer operational investigations to have access to change events that are recorded by CloudTrail. The default is <code>true</code>.</p>" |
| 327 | + "documentation":"<p>Specify <code>true</code> to enable CloudWatch investigations to have access to change events that are recorded by CloudTrail. The default is <code>true</code>.</p>" |
| 328 | + }, |
| 329 | + "crossAccountConfigurations":{ |
| 330 | + "shape":"CrossAccountConfigurations", |
| 331 | + "documentation":"<p>Number of <code>sourceAccountId</code> values that have been configured for cross-account access.</p>" |
328 | 332 | }
|
329 | 333 | }
|
330 | 334 | },
|
|
337 | 341 | }
|
338 | 342 | }
|
339 | 343 | },
|
| 344 | + "CrossAccountConfiguration":{ |
| 345 | + "type":"structure", |
| 346 | + "members":{ |
| 347 | + "sourceRoleArn":{ |
| 348 | + "shape":"RoleArn", |
| 349 | + "documentation":"<p>The ARN of an existing role which will be used to do investigations on your behalf. </p>" |
| 350 | + } |
| 351 | + }, |
| 352 | + "documentation":"<p>This structure contains information about the cross-account configuration in the account. </p>" |
| 353 | + }, |
| 354 | + "CrossAccountConfigurations":{ |
| 355 | + "type":"list", |
| 356 | + "member":{"shape":"CrossAccountConfiguration"}, |
| 357 | + "max":25, |
| 358 | + "min":0 |
| 359 | + }, |
340 | 360 | "DeleteInvestigationGroupPolicyOutput":{
|
341 | 361 | "type":"structure",
|
342 | 362 | "members":{
|
|
485 | 505 | },
|
486 | 506 | "isCloudTrailEventHistoryEnabled":{
|
487 | 507 | "shape":"Boolean",
|
488 |
| - "documentation":"<p>Specifies whether Amazon Q Developer operational investigationshas access to change events that are recorded by CloudTrail.</p>" |
| 508 | + "documentation":"<p>Specifies whether CloudWatch investigationshas access to change events that are recorded by CloudTrail.</p>" |
| 509 | + }, |
| 510 | + "crossAccountConfigurations":{ |
| 511 | + "shape":"CrossAccountConfigurations", |
| 512 | + "documentation":"<p>Lists the <code>AWSAccountId</code> of the accounts configured for cross-account access and the results of the last scan performed on each account.</p>" |
489 | 513 | }
|
490 | 514 | }
|
491 | 515 | },
|
|
594 | 618 | "members":{
|
595 | 619 | "resourceArn":{
|
596 | 620 | "shape":"String",
|
597 |
| - "documentation":"<p>The ARN of the Amazon Q Developer operational investigations resource that you want to view tags for. You can use the <a href=\"https://docs.aws.amazon.com/operationalinvestigations/latest/AmazonQDeveloperOperationalInvestigationsAPIReference/API_ListInvestigationGroups.html\">ListInvestigationGroups</a> operation to find the ARNs of investigation groups.</p> <p>The ARN format for an investigation group is <code>arn:aws:aiops:<i>Region</i>:<i>account-id</i>:investigation-group:<i>investigation-group-id</i> </code>.</p>", |
| 621 | + "documentation":"<p>The ARN of the CloudWatch investigations resource that you want to view tags for. You can use the <a href=\"https://docs.aws.amazon.com/operationalinvestigations/latest/AmazonQDeveloperOperationalInvestigationsAPIReference/API_ListInvestigationGroups.html\">ListInvestigationGroups</a> operation to find the ARNs of investigation groups.</p> <p>The ARN format for an investigation group is <code>arn:aws:aiops:<i>Region</i>:<i>account-id</i>:investigation-group:<i>investigation-group-id</i> </code>.</p>", |
598 | 622 | "location":"uri",
|
599 | 623 | "locationName":"resourceArn"
|
600 | 624 | }
|
|
806 | 830 | },
|
807 | 831 | "roleArn":{
|
808 | 832 | "shape":"RoleArn",
|
809 |
| - "documentation":"<p>Specify this field if you want to change the IAM role that Amazon Q Developer operational investigations will use when it gathers investigation data. To do so, specify the ARN of the new role.</p> <p>The permissions in this role determine which of your resources that Amazon Q Developer operational investigations will have access to during investigations.</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Security.html#Investigations-Security-Data\">EHow to control what data Amazon Q has access to during investigations</a>.</p>" |
| 833 | + "documentation":"<p>Specify this field if you want to change the IAM role that CloudWatch investigations will use when it gathers investigation data. To do so, specify the ARN of the new role.</p> <p>The permissions in this role determine which of your resources that CloudWatch investigations will have access to during investigations.</p> <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Security.html#Investigations-Security-Data\">EHow to control what data Amazon Q has access to during investigations</a>.</p>" |
810 | 834 | },
|
811 | 835 | "encryptionConfiguration":{
|
812 | 836 | "shape":"EncryptionConfiguration",
|
813 |
| - "documentation":"<p>Use this structure if you want to use a customer managed KMS key to encrypt your investigation data. If you omit this parameter, Amazon Q Developer operational investigations will use an Amazon Web Services key to encrypt the data. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Security.html#Investigations-KMS\">Encryption of investigation data</a>.</p>" |
| 837 | + "documentation":"<p>Use this structure if you want to use a customer managed KMS key to encrypt your investigation data. If you omit this parameter, CloudWatch investigations will use an Amazon Web Services key to encrypt the data. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Security.html#Investigations-KMS\">Encryption of investigation data</a>.</p>" |
814 | 838 | },
|
815 | 839 | "tagKeyBoundaries":{
|
816 | 840 | "shape":"TagKeyBoundaries",
|
817 | 841 | "documentation":"<p>Enter the existing custom tag keys for custom applications in your system. Resource tags help Amazon Q narrow the search space when it is unable to discover definite relationships between resources. For example, to discover that an Amazon ECS service depends on an Amazon RDS database, Amazon Q can discover this relationship using data sources such as X-Ray and CloudWatch Application Signals. However, if you haven't deployed these features, Amazon Q will attempt to identify possible relationships. Tag boundaries can be used to narrow the resources that will be discovered by Amazon Q in these cases.</p> <p>You don't need to enter tags created by myApplications or CloudFormation, because Amazon Q can automatically detect those tags.</p>"
|
818 | 842 | },
|
819 | 843 | "chatbotNotificationChannel":{
|
820 | 844 | "shape":"ChatbotNotificationChannel",
|
821 |
| - "documentation":"<p>Use this structure to integrate Amazon Q Developer operational investigations with Amazon Q in chat applications. This structure is a string array. For the first string, specify the ARN of an Amazon SNS topic. For the array of strings, specify the ARNs of one or more Amazon Q in chat applications configurations that you want to associate with that topic. For more information about these configuration ARNs, see <a href=\"https://docs.aws.amazon.com/chatbot/latest/adminguide/getting-started.html\">Getting started with Amazon Q in chat applications</a> and <a href=\"https://docs.aws.amazon.com/service-authorization/latest/reference/list_awschatbot.html#awschatbot-resources-for-iam-policies\">Resource type defined by Amazon Web Services Chatbot</a>.</p>" |
| 845 | + "documentation":"<p>Use this structure to integrate CloudWatch investigations with Amazon Q in chat applications. This structure is a string array. For the first string, specify the ARN of an Amazon SNS topic. For the array of strings, specify the ARNs of one or more Amazon Q in chat applications configurations that you want to associate with that topic. For more information about these configuration ARNs, see <a href=\"https://docs.aws.amazon.com/chatbot/latest/adminguide/getting-started.html\">Getting started with Amazon Q in chat applications</a> and <a href=\"https://docs.aws.amazon.com/service-authorization/latest/reference/list_awschatbot.html#awschatbot-resources-for-iam-policies\">Resource type defined by Amazon Web Services Chatbot</a>.</p>" |
822 | 846 | },
|
823 | 847 | "isCloudTrailEventHistoryEnabled":{
|
824 | 848 | "shape":"Boolean",
|
825 |
| - "documentation":"<p>Specify <code>true</code> to enable Amazon Q Developer operational investigations to have access to change events that are recorded by CloudTrail. The default is <code>true</code>.</p>" |
| 849 | + "documentation":"<p>Specify <code>true</code> to enable CloudWatch investigations to have access to change events that are recorded by CloudTrail. The default is <code>true</code>.</p>" |
| 850 | + }, |
| 851 | + "crossAccountConfigurations":{ |
| 852 | + "shape":"CrossAccountConfigurations", |
| 853 | + "documentation":"<p>Used to configure cross-account access for an investigation group. It allows the investigation group to access resources in other accounts. </p>" |
826 | 854 | }
|
827 | 855 | }
|
828 | 856 | },
|
|
839 | 867 | "exception":true
|
840 | 868 | }
|
841 | 869 | },
|
842 |
| - "documentation":"<p>The Amazon Q Developer operational investigations feature is a generative AI-powered assistant that can help you respond to incidents in your system. It uses generative AI to scan your system's telemetry and quickly surface suggestions that might be related to your issue. These suggestions include metrics, logs, deployment events, and root-cause hypotheses. </p> <p>You can use API actions to create, manage, and delete investigation groups and investigation group policies. To start and manage investigations, you must use the CloudWatch console.</p>" |
| 870 | + "documentation":"<p>The CloudWatch investigations feature is a generative AI-powered assistant that can help you respond to incidents in your system. It uses generative AI to scan your system's telemetry and quickly surface suggestions that might be related to your issue. These suggestions include metrics, logs, deployment events, and root-cause hypotheses. </p> <p>You can use API actions to create, manage, and delete investigation groups and investigation group policies. To start and manage investigations, you must use the CloudWatch console.</p>" |
843 | 871 | }
|
0 commit comments