Unable to select certain CloudWatch log groups as Lambda triggers by name

Question

I'm working within a decently large system and I ran into an issue trying to set up a Lambda that ingests logs from various CloudWatch log groups. (Resource names below slightly changed.)

One of the services spits out logs to an admittedly-nonstandard-looking CloudWatch Log Group (no `/` in the name, just a kebab-case set of words, let's say it's basically `dev-service-name-log-group`). When I go to the Lambda, if I select "Add Trigger", "CloudWatch Logs", I get a dropdown with all of the many, many `/aws/whatever` log groups but not this one or any other similar ones. I checked and confirmed they must be being filtered out on the server side, not just in the client-side code. But I also checked and I can retrieve my `dev-service-name-log-group` listing from the CLI, it is in fact a valid log group with that name.

Answer

FYI we can do this without a problem - maybe you have a lot more "/aws/whatever" groups than we do though?

![](/media/postImages/original/IMckkaYglrTuSdxntsDkrw_A)

Answer

You raise a good point - I think it might actually be that there's a limit on how many log groups it queries for (it looks like it might be around 1000), although I would think that if I explicitly type in a value, it shouldn't refuse to accept it in that case.

Unable to select certain CloudWatch log groups as Lambda triggers by name

Relevanter Inhalt