- Newest
- Most votes
- Most comments
Hi Arthur,
Thank you for your response. Luke Klaassen will be reaching out to you shortly. As a workaround for this issue, please note that the session id is written to: /opt/amazon/nimblestudio/bin/nimble-agent.sh. I believe you can access the session ID there.
Please feel free to reach back out if Luke Klaassen has not contacted you.
Best, Calvin
Hi Arthur,
I checked with Nimble Studio Engineering. Please note that unlike EC2 spot instances which offer a notification within the instance, Nimble Studio does not have such a notification within the instance. The customer must build a custom notification mechanism to query streaming sessions (nimble:ListStreamingSessions) in their account and monitor the stopAt timestamp which will be future dated based on the session length they choose. Please feel free to respond with any questions!
Best, Calvin
Hi Arthur,
Thank you for your response and additional context. Please note that you can find the session ID in the Nimble agent on the streaming instance. Can you please confirm what platform you are using? Then, I'll revert back with additional detail.
Best, Calvin
Hi Calvin,
Thank you, we use CentOS 7.
Best regards, Arthur Uzulin
Relevant content
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 8 months ago
Hi Calvin,
Thank you for looking into this, I am trying to build this solution for our pipeline now, but I am struggling to find a way to get the Nimble Studio session id from within the session to use alongside list-streaming-sessions (or get-streaming-session) to find the data pertinent to the current session rather than all sessions.
Would there be anything that would allow this? On the EC2 side, I can curl http://169.254.169.254/latest/meta-data/instance-id to get the EC2 instance id, but I fail to see anything like this for the streaming session id.