I have tested how to use functionbeat for AWS cloudwatch via lambda function. But when i deploy funtionbeat, stack creating is failed after the following error generating. # ./functionbeat -v -e -d "*" deploy cloudwatch <snip> Stack event received, ResourceType: AWS::Logs::SubscriptionFilter, Log…

[image] kvch: log g Hi, Ványi I thought that bucket and function, trigger(log group) for AWS is created by Deploy but that was wrong. When I created manually configured trigger on AWS Cloudwatch log group Before deploying, All operations/deploy is successful. I can know that the below sho…

Failed to create the stack. AWS Lambda Stack event CREATE_FAILED, ResourceStatusReason: The specified log group does not exist

Elastic Stack Beats

system (system) Closed September 8, 2020, 2:36am 4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
ResourceStatus: CREATE_FAILED, ResourceStatusReason: Resource handler returned message: \"The specified log group does not exist Beats functionbeat	2	1128	October 11, 2022
Functionbeat fails to update with a new cloudwatch log group Could not execute the lambda function Beats functionbeat	2	731	November 11, 2022
The specified log group does not exist. Error when configuring lambda function for cloudwatch logs Elasticsearch	1	761	July 26, 2021
Function: cloudwatch, could not deploy, error: bucket 'trial' already exist and you don't have permission to access it Beats functionbeat	1	1204	February 21, 2020
Could not create the CloudFormation stack request Beats functionbeat	5	615	February 24, 2022

Failed to create the stack. AWS Lambda Stack event CREATE_FAILED, ResourceStatusReason: The specified log group does not exist

Related topics