class
Amazonite::CloudWatchLogs::PutDataProtectionPolicyRequest
- Amazonite::CloudWatchLogs::PutDataProtectionPolicyRequest
- Reference
- Object
Included Modules
- JSON::Serializable
Defined in:
cloudwatch_logs/put_data_protection_policy_request.crConstructors
- .new(log_group_identifier : String, policy_document : String)
- .new(pull : JSON::PullParser)
- .new(*, __pull_for_json_serializable pull : JSON::PullParser)
Instance Method Summary
-
#==(other : self)
Returns
trueif this reference is the same as other. -
#hash(hasher)
See
Object#hash(hasher) -
#log_group_identifier : String
Specify either the log group name or log group ARN.
-
#log_group_identifier=(log_group_identifier : String)
Specify either the log group name or log group ARN.
-
#policy_document : String
Specify the data protection policy, in JSON.
-
#policy_document=(policy_document : String)
Specify the data protection policy, in JSON.
- #validate! : Nil
Constructor Detail
Instance Method Detail
Returns true if this reference is the same as other. Invokes same?.
Specify either the log group name or log group ARN.
Specify the data protection policy, in JSON.
This policy must include two JSON blocks:
- The first block must include both a
DataIdentiferarray and anOperationproperty with anAuditaction. TheDataIdentiferarray lists the types of sensitive data that you want to mask. For more information about the available options, see Types of data that you can mask.
The Operation property with an Audit action is required to find the sensitive data terms.
This Audit action must contain a FindingsDestination object. You can optionally use that
FindingsDestination object to list one or more destinations to send audit findings to. If you
specify destinations such as log groups, Firehose streams, and S3 buckets, they must already
exist.
- The second block must include both a
DataIdentiferarray and anOperationproperty with anDeidentifyaction. TheDataIdentiferarray must exactly match theDataIdentiferarray in the first block of the policy.
The Operation property with the Deidentify action is what actually masks the data, and it
must contain the "MaskConfig": {} object. The "MaskConfig": {} object must be empty.
For an example data protection policy, see the Examples section on this page.
The contents of the two DataIdentifer arrays must match exactly.
In addition to the two JSON blocks, the policyDocument can also include Name, Description,
and Version fields. The Name is used as a dimension when CloudWatch Logs reports audit
findings metrics to CloudWatch.
The JSON specified in policyDocument can be up to 30,720 characters.
Specify the data protection policy, in JSON.
This policy must include two JSON blocks:
- The first block must include both a
DataIdentiferarray and anOperationproperty with anAuditaction. TheDataIdentiferarray lists the types of sensitive data that you want to mask. For more information about the available options, see Types of data that you can mask.
The Operation property with an Audit action is required to find the sensitive data terms.
This Audit action must contain a FindingsDestination object. You can optionally use that
FindingsDestination object to list one or more destinations to send audit findings to. If you
specify destinations such as log groups, Firehose streams, and S3 buckets, they must already
exist.
- The second block must include both a
DataIdentiferarray and anOperationproperty with anDeidentifyaction. TheDataIdentiferarray must exactly match theDataIdentiferarray in the first block of the policy.
The Operation property with the Deidentify action is what actually masks the data, and it
must contain the "MaskConfig": {} object. The "MaskConfig": {} object must be empty.
For an example data protection policy, see the Examples section on this page.
The contents of the two DataIdentifer arrays must match exactly.
In addition to the two JSON blocks, the policyDocument can also include Name, Description,
and Version fields. The Name is used as a dimension when CloudWatch Logs reports audit
findings metrics to CloudWatch.
The JSON specified in policyDocument can be up to 30,720 characters.