Lambda function cannot write logs to Cloudwatch

[viyullas]

SUMMARY

Probably it has been some change on AWS, because a disclaimer shows asking to add a policy to the execution role used by the Lambda function: AWSLambdaBasicExecutionRole

ISSUE TYPE

• Bug Report

TERRAFORM VERSION

Terraform v0.14.0
+ provider registry.terraform.io/hashicorp/archive v2.1.0
+ provider registry.terraform.io/hashicorp/aws v3.26.0
+ provider registry.terraform.io/hashicorp/local v2.0.0
+ provider registry.terraform.io/hashicorp/null v3.0.0
+ provider registry.terraform.io/hashicorp/random v3.0.1
+ provider registry.terraform.io/hashicorp/template v2.2.0
+ provider registry.terraform.io/terraform-providers/mysql v1.9.0

Your version of Terraform is out of date! The latest version
is 0.14.7. You can update by downloading from https://www.terraform.io/downloads.htm

STEPS TO REPRODUCE

If you deploy de terraform module as is a disclaimer appears when you try to see the logs from the lambda funcions page on aws web console

module "start_environment" {
  count                          = local.settings.schedulling_enabled == false ? 0 : 1
  source                         = "diodonfrost/lambda-scheduler-stop-start/aws"
  name                           = "ec2_start"
  cloudwatch_schedule_expression = local.settings.env_start
  aws_regions                    = [local.settings.aws_region]
  schedule_action                = "start"
  autoscaling_schedule           = "true"
  ec2_schedule                   = "true"
  rds_schedule                   = "true"
  resources_tag = {
    key   = "Environment"
    value = terraform.workspace
  }

  tags = local.tags
}

EXPECTED RESULTS

Be able to watch logs

ACTUAL RESULTS

No logs.
If you manually add the role everything works as expected

[diodonfrost]

Thanks for your report, I think you are right. I'm going to investigate and write a fix when applicable.

[diodonfrost]

Fixed in version 3.1.1
thanks for your input!

[viyullas]

Hello!
I am having extrange behaviours with the latest release.
It has stopped responding to my custom tags, it sets "tostop" whether I configure another tag or not.

I still get the warning on lambda monitoring screen, I have not been able to see any log on cloudwath.

[nk9]

This sounds like a different issue, which should probably be opened separately. Isn't this issue ready to be closed?