Struct UpdateInvestigationGroupInput 

#[non_exhaustive]
pub struct UpdateInvestigationGroupInput {
    pub identifier: Option<String>,
    pub role_arn: Option<String>,
    pub encryption_configuration: Option<EncryptionConfiguration>,
    pub tag_key_boundaries: Option<Vec<String>>,
    pub chatbot_notification_channel: Option<HashMap<String, Vec<String>>>,
    pub is_cloud_trail_event_history_enabled: Option<bool>,
    pub cross_account_configurations: Option<Vec<CrossAccountConfiguration>>,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

identifier: Option<String>

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

role_arn: Option<String>

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.

encryption_configuration: Option<EncryptionConfiguration>

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.

tag_key_boundaries: Option<Vec<String>>

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.

chatbot_notification_channel: Option<HashMap<String, Vec<String>>>

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.

is_cloud_trail_event_history_enabled: Option<bool>

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

cross_account_configurations: Option<Vec<CrossAccountConfiguration>>

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

Implementations

impl UpdateInvestigationGroupInput

pub fn identifier(&self) -> Option<&str>

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

pub fn role_arn(&self) -> Option<&str>

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.

pub fn encryption_configuration(&self) -> Option<&EncryptionConfiguration>

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.

pub fn tag_key_boundaries(&self) -> &[String]

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.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .tag_key_boundaries.is_none().

pub fn chatbot_notification_channel( &self, ) -> Option<&HashMap<String, Vec<String>>>

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.

pub fn is_cloud_trail_event_history_enabled(&self) -> Option<bool>

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

pub fn cross_account_configurations(&self) -> &[CrossAccountConfiguration]

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

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .cross_account_configurations.is_none().

impl UpdateInvestigationGroupInput

pub fn builder() -> UpdateInvestigationGroupInputBuilder

Creates a new builder-style object to manufacture UpdateInvestigationGroupInput.

Trait Implementations

impl Clone for UpdateInvestigationGroupInput

fn clone(&self) -> UpdateInvestigationGroupInput

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for UpdateInvestigationGroupInput

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for UpdateInvestigationGroupInput

fn eq(&self, other: &UpdateInvestigationGroupInput) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for UpdateInvestigationGroupInput