Anton Uspishnyi

```bash ~ source ~/.zshrc /Users/anton/.zshrc:source:123: no such file or directory: /usr/local/share/zsh/site-functions/cw ~ ls -la /usr/local/share/zsh/site-functions/cw* lrwxr-xr-x 1 anton admin 56 Apr 26 10:30 /usr/local/share/zsh/site-functions/cw.zsh -> ../../../Cellar/cw/4.1.0/share/zsh/site-functions/cw.zsh ```

@pkasravi I have the same exact error using this github-action. Do you have a workaround?

@pkasravi It would be great if you could share the example of your solution or some snippet.

Hi everyone! Can you suggest here the right way to get rid of these noisy alerts? What is the current workaround for this?

Hi @rawrgulmuffins @Blake- You should use `awslogs --aws-region` instead of `--aws_region or --region`

@simtcrom you should use `--aws-region` instead. I had the same issue, it's not so obvious :)

Hi @jordisantamaria @xinhuagu You should to define the `log_group_name` to search streams in it. It's a positional argument. For example (replace group name): ```sh awslogs streams '/aws/lambda/cdkworkshop-HelloHandler2E4FBA4D-j0QXnaK050Xv' ```

Even if you try plain? ```sh awslogs get "/aws/lambda/test" ``` Maybe they are too old and you have to set `--start` argument to try find older ones.

> > Even if you try plain? > > > > > > ```shell > > > awslogs get "/aws/lambda/test" > > > ``` > > > > > >...