-
|
Are sessions opened by ssm-agent suppose to be getting logged in journald? I would expect to see those under control-container logs, but they don't show up. bash-5.1# journalctl -u [email protected]
-- No entries -- |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
Thanks for reaching out, @hi-artem! They are not logged on the host side today. You can see the sessions by querying Systems Manager itself either through the web console or CLI (using |
Beta Was this translation helpful? Give feedback.
-
|
@jpculp Thank you for answering the question. Tracking sessions based on Session Manager events works for our particular use-case. No need to open a feature request. |
Beta Was this translation helpful? Give feedback.
-
|
Is this still the case? Are SSM logs stored anywhere on the host? (where a centralized log system might be able to scrape them?) or do we have to rely on cloudwatch/s3? |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Thanks for reaching out. Could you share more details about your use case? We're happy to open a Feature Request if needed. |
Beta Was this translation helpful? Give feedback.
-
|
We have a daemonset on every node that collects pod logs and some node logs for our centralized log pipeline (Vector + Loki). We’d like to have it be able to ingest logs from SSM sessions started on the host. We’d can do this on AL2, but not bottle rocket
…On Fri, Jan 17, 2025 at 2:02 PM, Vighnesh Maheshwari ***@***.***(mailto:On Fri, Jan 17, 2025 at 2:02 PM, Vighnesh Maheshwari <<a href=)> wrote:
Hi! Thanks for reaching out.
I verified with the latest AMI release right now (v1.30.0) and this remains the case. Using aws ssm describe-sessions --state History and other AWS tooling is still the best way to get this information.
Could you share more details about your use case? We're happy to open a Feature Request if needed.
—
Reply to this email directly, [view it on GitHub](#2432 (reply in thread)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AC7XW4UBS5Z3V5ALRK4IARL2LFHT3AVCNFSM6AAAAABVKRFWBGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBXGA2TQMQ).
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Thanks for reaching out, @hi-artem! They are not logged on the host side today. You can see the sessions by querying Systems Manager itself either through the web console or CLI (using
aws ssm describe-sessions --state History). You can also configure Systems Manager to log sessions to CloudWatch or S3. If you'd still like to see this on the host itself, please let us know and we can create a feature request for you.