Skip to content

/AWS1/IF_AIO=>UPDATEINVESTIGATIONGROUP()

About UpdateInvestigationGroup

Updates the configuration of the specified investigation group.

Method Signature

METHODS /AWS1/IF_AIO~UPDATEINVESTIGATIONGROUP
  IMPORTING
    !IV_IDENTIFIER TYPE /AWS1/AIOINVESTIGATIONGROUPID OPTIONAL
    !IV_ROLEARN TYPE /AWS1/AIOROLEARN OPTIONAL
    !IO_ENCRYPTIONCONFIGURATION TYPE REF TO /AWS1/CL_AIOENCRYPTIONCONF OPTIONAL
    !IT_TAGKEYBOUNDARIES TYPE /AWS1/CL_AIOTAGKEYBOUNDARIES_W=>TT_TAGKEYBOUNDARIES OPTIONAL
    !IT_CHATBOTNOTIFCHANNEL TYPE /AWS1/CL_AIOCHATCONFARNS_W=>TT_CHATBOTNOTIFICATIONCHANNEL OPTIONAL
    !IV_ISCLOUDTRAILEVTHISTORYE00 TYPE /AWS1/AIOBOOLEAN OPTIONAL
    !IT_CROSSACCOUNTCONFS TYPE /AWS1/CL_AIOCROSSACCOUNTCONF=>TT_CROSSACCOUNTCONFIGURATIONS OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_aioupinvestigationg01
  RAISING
    /AWS1/CX_AIOACCESSDENIEDEX
    /AWS1/CX_AIOCONFLICTEXCEPTION
    /AWS1/CX_AIOFORBIDDENEXCEPTION
    /AWS1/CX_AIOINTERNALSERVEREX
    /AWS1/CX_AIORESOURCENOTFOUNDEX
    /AWS1/CX_AIOVALIDATIONEX
    /AWS1/CX_AIOTHROTTLINGEX
    /AWS1/CX_AIOCLIENTEXC
    /AWS1/CX_AIOSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING

Required arguments:

iv_identifier TYPE /AWS1/AIOINVESTIGATIONGROUPID /AWS1/AIOINVESTIGATIONGROUPID

Specify either the name or the ARN of the investigation group that you want to modify.

Optional arguments:

iv_rolearn TYPE /AWS1/AIOROLEARN /AWS1/AIOROLEARN

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.

The permissions in this role determine which of your resources that CloudWatch investigations will have access to during investigations.

For more information, see How to control what data CloudWatch investigations has access to during investigations.

io_encryptionconfiguration TYPE REF TO /AWS1/CL_AIOENCRYPTIONCONF /AWS1/CL_AIOENCRYPTIONCONF

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 Encryption of investigation data.

it_tagkeyboundaries TYPE /AWS1/CL_AIOTAGKEYBOUNDARIES_W=>TT_TAGKEYBOUNDARIES TT_TAGKEYBOUNDARIES

Enter the existing custom tag keys for custom applications in your system. Resource tags help CloudWatch investigations 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, CloudWatch investigations can discover this relationship using data sources such as X-Ray and CloudWatch Application Signals. However, if you haven't deployed these features, CloudWatch investigations will attempt to identify possible relationships. Tag boundaries can be used to narrow the resources that will be discovered by CloudWatch investigations in these cases.

You don't need to enter tags created by myApplications or CloudFormation, because CloudWatch investigations can automatically detect those tags.

it_chatbotnotifchannel TYPE /AWS1/CL_AIOCHATCONFARNS_W=>TT_CHATBOTNOTIFICATIONCHANNEL TT_CHATBOTNOTIFICATIONCHANNEL

Use this structure to integrate CloudWatch investigations with 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 chat applications configurations that you want to associate with that topic. For more information about these configuration ARNs, see Getting started with Amazon Q in chat applications and Resource type defined by Amazon Web Services Chatbot.

iv_iscloudtrailevthistorye00 TYPE /AWS1/AIOBOOLEAN /AWS1/AIOBOOLEAN

Specify true to enable CloudWatch investigations to have access to change events that are recorded by CloudTrail. The default is true.

it_crossaccountconfs TYPE /AWS1/CL_AIOCROSSACCOUNTCONF=>TT_CROSSACCOUNTCONFIGURATIONS TT_CROSSACCOUNTCONFIGURATIONS

Used to configure cross-account access for an investigation group. It allows the investigation group to access resources in other accounts.

RETURNING

oo_output TYPE REF TO /aws1/cl_aioupinvestigationg01 /AWS1/CL_AIOUPINVESTIGATIONG01

Domain /AWS1/RT_ACCOUNT_ID
Primitive Type NUMC

Examples

Syntax Example

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->updateinvestigationgroup(
  io_encryptionconfiguration = new /aws1/cl_aioencryptionconf(
    iv_kmskeyid = |string|
    iv_type = |string|
  )
  it_chatbotnotifchannel = VALUE /aws1/cl_aiochatconfarns_w=>tt_chatbotnotificationchannel(
    (
      VALUE /aws1/cl_aiochatconfarns_w=>ts_chatbotnotifchannel_maprow(
        value = VALUE /aws1/cl_aiochatconfarns_w=>tt_chatconfigurationarns(
          ( new /aws1/cl_aiochatconfarns_w( |string| ) )
        )
        key = |string|
      )
    )
  )
  it_crossaccountconfs = VALUE /aws1/cl_aiocrossaccountconf=>tt_crossaccountconfigurations(
    ( new /aws1/cl_aiocrossaccountconf( |string| ) )
  )
  it_tagkeyboundaries = VALUE /aws1/cl_aiotagkeyboundaries_w=>tt_tagkeyboundaries(
    ( new /aws1/cl_aiotagkeyboundaries_w( |string| ) )
  )
  iv_identifier = |string|
  iv_iscloudtrailevthistorye00 = ABAP_TRUE
  iv_rolearn = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
ENDIF.