Log group does not exist error when using aws lambda

Question

I'm using aws SQS to trigger a lambda function, after I send message to sqs, when I want to see the cloudwatch log in lambda, I got this error. I'm in the same aws region, any idea what this happened?

Log group does not exist
The specific log group: /aws/lambda/configurationTest does not exist in this account or region

If you go to Lambda Fxn > Monitor > Logs, do you see entries under 'Recent Invocations'? — akskap
– akskap, Commented Jun 4, 2021 at 19:41
Make sure your Lambda invocation role has access to CloudWatch Log. — Avinash Dalvi
– Avinash Dalvi, Commented Jun 4, 2021 at 20:58

Ashutosh_Agarwal · Accepted Answer · 2022-08-10 09:28:25Z

11

Invoke lambda for the first time, it will create the log group.

answered Aug 10, 2022 at 9:28

Ashutosh_Agarwal

1191 silver badge4 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

louisdeb Over a year ago

This was actually helpful. For lambdas that did not have log groups, it was an indication that I had not successfully made a call to the lambda. One way of jogging this is by making a 'test' call from the AWS console.

Avinash Dalvi · Accepted Answer · 2021-06-04 21:03:55Z

9

This error happen when newly created Lambda execution role doesn't have access CloudWatch log write access.

Steps :

Go to IAM
Select role and add policy to write CloudWatch log.

answered Jun 4, 2021 at 21:03

Avinash Dalvi

9,4299 gold badges34 silver badges60 bronze badges

3 Comments

Avinash Dalvi Over a year ago

Don't forget to upvote answer if this help you.

Kash Over a year ago

I had the same issue with aws glue python shell job

Avinash Dalvi Over a year ago

not sure about aws glue. but hint is if any service not able to access other then obvious IAM issue.

Nik V · Accepted Answer · 2023-03-15 12:43:09Z

If you are using multiple lambda functions to have the same execution role (not recommended) you should explicitly specify each lambda ARN in the resource of the cloudwatch policy. As an example:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "logs:CreateLogGroup",
            "Resource": "arn:aws:logs:REGION:ACCOUNT_ID:*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "logs:CreateLogStream",
                "logs:PutLogEvents"
            ],
            "Resource": [
                "arn:aws:logs:REGION:ACCOUNT_ID:log-group:/aws/lambda/main_function:*",
                "arn:aws:logs:REGION:ACCOUNT_ID:log-group:/aws/lambda/second_function:*"
            ]
        }
    ]
}

This way your functions will be able to create log_group for each function.

Collectives™ on Stack Overflow

Log group does not exist error when using aws lambda

3 Answers 3

2 Comments

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related