Put Account Policy
cloudwatchlogs_put_account_policy | R Documentation |
Creates an account-level data protection policy or subscription filter policy that applies to all log groups or a subset of log groups in the account¶
Description¶
Creates an account-level data protection policy or subscription filter policy that applies to all log groups or a subset of log groups in the account.
Data protection policy
A data protection policy can help safeguard sensitive data that's ingested by your log groups by auditing and masking the sensitive log data. Each account can have only one account-level data protection policy.
Sensitive data is detected and masked when it is ingested into a log group. When you set a data protection policy, log events ingested into the log groups before that time are not masked.
If you use put_account_policy
to create a data protection policy for
your whole account, it applies to both existing log groups and all log
groups that are created later in this account. The account-level policy
is applied to existing log groups with eventual consistency. It might
take up to 5 minutes before sensitive data in existing log groups begins
to be masked.
By default, when a user views a log event that includes masked data, the
sensitive data is replaced by asterisks. A user who has the
logs:Unmask
permission can use a get_log_events
or
filter_log_events
operation with the unmask
parameter set to true
to view the unmasked log events. Users with the logs:Unmask
can also
view unmasked data in the CloudWatch Logs console by running a
CloudWatch Logs Insights query with the unmask
query command.
For more information, including a list of types of data that can be audited and masked, see Protect sensitive log data with masking.
To use the put_account_policy
operation for a data protection policy,
you must be signed on with the logs:PutDataProtectionPolicy
and
logs:PutAccountPolicy
permissions.
The put_account_policy
operation applies to all log groups in the
account. You can use put_data_protection_policy
to create a data
protection policy that applies to just one log group. If a log group has
its own data protection policy and the account also has an account-level
data protection policy, then the two policies are cumulative. Any
sensitive term specified in either policy is masked.
Subscription filter policy
A subscription filter policy sets up a real-time feed of log events from CloudWatch Logs to other Amazon Web Services services. Account-level subscription filter policies apply to both existing log groups and log groups that are created later in this account. Supported destinations are Kinesis Data Streams, Firehose, and Lambda. When log events are sent to the receiving service, they are Base64 encoded and compressed with the GZIP format.
The following destinations are supported for subscription filters:
-
An Kinesis Data Streams data stream in the same account as the subscription policy, for same-account delivery.
-
An Firehose data stream in the same account as the subscription policy, for same-account delivery.
-
A Lambda function in the same account as the subscription policy, for same-account delivery.
-
A logical destination in a different account created with
put_destination
, for cross-account delivery. Kinesis Data Streams and Firehose are supported as logical destinations.
Each account can have one account-level subscription filter policy per
Region. If you are updating an existing filter, you must specify the
correct name in PolicyName
. To perform a put_account_policy
subscription filter operation for any destination except a Lambda
function, you must also have the iam:PassRole
permission.
Usage¶
Arguments¶
policyName
[required] A name for the policy. This must be unique within the account.
policyDocument
[required] Specify the policy, in JSON.
Data protection policy
A data protection policy must include two JSON blocks:
The first block must include both a
DataIdentifer
array and anOperation
property with anAudit
action. TheDataIdentifer
array 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 anAudit
action is required to find the sensitive data terms. ThisAudit
action must contain aFindingsDestination
object. You can optionally use thatFindingsDestination
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
DataIdentifer
array and anOperation
property with anDeidentify
action. TheDataIdentifer
array must exactly match theDataIdentifer
array in the first block of the policy.The
Operation
property with theDeidentify
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 includeName
,Description
, andVersion
fields. TheName
is different than the operation'spolicyName
parameter, and 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 long.Subscription filter policy
A subscription filter policy can include the following attributes in a JSON block:
DestinationArn The ARN of the destination to deliver log events to. Supported destinations are:
An Kinesis Data Streams data stream in the same account as the subscription policy, for same-account delivery.
An Firehose data stream in the same account as the subscription policy, for same-account delivery.
A Lambda function in the same account as the subscription policy, for same-account delivery.
A logical destination in a different account created with
put_destination
, for cross-account delivery. Kinesis Data Streams and Firehose are supported as logical destinations.
RoleArn The ARN of an IAM role that grants CloudWatch Logs permissions to deliver ingested log events to the destination stream. You don't need to provide the ARN when you are working with a logical destination for cross-account delivery.
FilterPattern A filter pattern for subscribing to a filtered stream of log events.
Distribution The method used to distribute log data to the destination. By default, log data is grouped by log stream, but the grouping can be set to
Random
for a more even distribution. This property is only applicable when the destination is an Kinesis Data Streams data stream.
policyType
[required] The type of policy that you're creating or updating.
scope
Currently the only valid value for this parameter is
ALL
, which specifies that the data protection policy applies to all log groups in the account. If you omit this parameter, the default ofALL
is used.selectionCriteria
Use this parameter to apply the subscription filter policy to a subset of log groups in the account. Currently, the only supported filter is
LogGroupName NOT IN []
. TheselectionCriteria
string can be up to 25KB in length. The length is determined by using its UTF-8 bytes.Using the
selectionCriteria
parameter is useful to help prevent infinite loops. For more information, see Log recursion prevention.Specifing
selectionCriteria
is valid only when you specifySUBSCRIPTION_FILTER_POLICY
forpolicyType
.
Value¶
A list with the following syntax:
list(
accountPolicy = list(
policyName = "string",
policyDocument = "string",
lastUpdatedTime = 123,
policyType = "DATA_PROTECTION_POLICY"|"SUBSCRIPTION_FILTER_POLICY",
scope = "ALL",
selectionCriteria = "string",
accountId = "string"
)
)