The ARN of the AWS IAM Role with permission to read CloudWatch log groups
false
cloudwatch_regions
string
comma-separated regions to query for CloudWatch log groups in
false
sso_identity_store_id
string
the AWS SSO identity store ID
false
sso_instance_arn
string
the AWS SSO instance ARN
false
sso_region
string
the AWS SSO instance region
false
sso_role_arn
string
The ARN of the AWS IAM Role with permission to create AWS SSO Permission Sets
false
Docs
Access
This Access Provider provisions a temporary AWS IAM Identity Center Permission Set which grants access to read a CloudWatch log group. When making an access request, users will specify the following parameters:
Parameter
Description
log_group
the ARN of the CloudWatch log group to grant read access to
The Access Provider provisions a Permission Set and attaches the following inline policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"logs:GetLogDelivery",
"logs:GetLogEvents",
"logs:GetLogGroupFields",
"logs:GetLogRecord",
"logs:GetQueryResults",
"logs:StartQuery",
"logs:StopQuery",
"logs:TestMetricFilter",
"logs:FilterLogEvents",
"logs:DescribeSubscriptionFilters",
"logs:ListTagsLogGroup",
"logs:GetDataProtectionPolicy",
],
"Resource": [f"{target.log_group}:*"],
},
// These permissions are not required to view log group data,
// but allowing users to view metadata about logs results in
// a far better console user experience.
//
// This allows for users to view metadata about log groups
// other than the one they have requested, and to view
// metric data. This provider does not consider these to be
// sensitive and in fact may be of assistance to a user who
// is using this provider to get access to logs when responding
// to an incident.
//
// In future we will introduce a configuration option allowing
// this policy statement to be disabled, so that metadata
// about other log groups and metrics cannot be viewed.
{
"Effect": "Allow",
"Action": [
"logs:DescribeLogGroups",
"logs:DescribeLogStreams",
"logs:DescribeMetricFilters",
"cloudwatch:GetMetricData",
],
"Resource": ["*"],
},
],
}
Deployment architecture
We recommend the adopting the following account architecture when deploying this Access Provider:
The Access Provider should be deployed in the same AWS account as your Common Fate deployment.
You will also need AWS credentials with the ability to deploy CloudFormation templates.
To use this Access Provider, you need to have AWS IAM Identity Center set up in your AWS Organization. Please contact us via Slack if you'd like to use this Access Provider, but are not using IAM Identity Center.
1. Deploy access roles
First, deploy the IAM roles below.
CloudWatch read role
This role is used to list CloudWatch log groups to determine the available log groups for users to select.
Deploy this role into the account with the log groups you wish to grant access to:
AWS SSO provisioning role
This role allows the Access Provider to create temporary Permission Sets in IAM Identity Center, and attach an inline policy allowing read access to CloudWatch log data.
Deploy this role into either the root account of your AWS organization, or into an account which is given Delegated Administration privileges:
2. Deploy the Access Provider
To deploy this Access Provider, open a terminal window and assume an AWS role with access to deploy CloudFormation resources in the Common Fate account. Then, run:
cf provider deploy
and select the common-fate/cloudwatch-log-groups Provider when prompted.
Common Fate is a platform that automatically manages access to cloud infrastructure and vital applications, providing users with limited, time-sensitive permissions. It records and audits access data, simplifying compliance and governance processes.
Yes! Registry encourages developers to create and share their own identity and access management providers. By contributing to the registry, you can help expand the range of solutions available to organizations and showcase your expertise in the IAM field.
By using the Common Fate Registry, your organization can access a wide range of official and community-created identity and access management providers. This allows you to customize and enhance your security infrastructure, improve user management workflows, and stay up-to-date with the latest advancements in IAM.
For further information and support, be sure to join our Slack Community.