Read your AWS CloudWatch logs, including Lambda logs, without leaving the IDE. This page walks through it in the order you will actually do it.
After installing, the tool window sits at the bottom of the IDE as CloudWatch Logs. If it is not showing, use View → Tool Windows → CloudWatch Logs.
The panel opens beside your code, so you never leave the IDE to read a log.
Fill in Region. Leave Profile empty to use your
default credentials, or name a profile from ~/.aws/config. Credentials come
from the files, environment variables and SSO sessions you already have; nothing is
uploaded anywhere, and no call is made until you ask for one.
Endpoint is only for a local stand-in such as LocalStack. Leave it empty for real AWS.
Open the drop-down and choose the group, for example
/aws/lambda/checkout-api. The refresh button beside it re-reads the list
when you have just created a group. The star keeps a group at the top of the list so
you are not scrolling for it tomorrow.
Pick a range (Last 1 hour and so on), type a word in Filter if you only want matching lines, then press Load.
Select any row and the whole message opens underneath. JSON is indented for you, so a payload is readable without copying it somewhere else.
Errors and their stack traces arrive as ordinary rows, in order, so you can read down from the message that failed to the line that threw.
The row count at the bottom tells you how much you are looking at.
Live keeps the newest lines arriving while you work. Save writes what is on screen to a file. Both are part of the paid tier.
Finding and browsing your log groups is free and stays free. Reading log events, live tail, saving what is on screen and favorites need a licence, and every paid feature is included in a 30-day trial that needs no card. Buying and invoicing are handled by JetBrains.
Only logs:DescribeLogGroups, logs:FilterLogEvents and
logs:GetLogEvents.
globalmatchhub@gmail.com. We aim to reply within two business days.