Naw, the CloudWatch log groups should automatically be created. They get created when the lambda functions execute. Wondering if you could try hitting the lambda function directly in the Lambda Console (web browser). Then after that, check CloudWatch logs. You should see the Log group to verify that the lambda function ran.
Here are also some video and tutorials that may help:
- Jets Debugging CloudWatch Logs - Useful CloudWatch log intro.
- Jets Tutorial Debugging Logs Part 3: AWS Lambda Ruby - Shows how to find the log group with a demo Jets application deployed.
- AWS Lambda Function: Jets AWS Introduction Series Part 1 - This covers AWS Lambda function essentials. This shows the process of creating a Lambda function manual. Jets automates this for you but found it to be helpful for folks.
Had another thought. Wondering if your AWS Lambda console is in the right region. Try running aws logs describe-log-groups from the terminal where you deployed the Jets application. It should show the log groups that way also. Also, aws lambda list-functions should show the deployed functions.
Think here’s a similar question