Recently we encountered an edge case where a user had the aws credentials file open for editing then created a new session. Upon closing the credentials file the AWS access key ID was not saved and subsequent access was denied. This behavior is expected!
It would benefit users to be able to check session status proactively on occasion and possibly throw a warning if an active session is detected
https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_DescribeSessions.html
Recently we encountered an edge case where a user had the aws credentials file open for editing then created a new session. Upon closing the credentials file the AWS access key ID was not saved and subsequent access was denied. This behavior is expected!
It would benefit users to be able to check session status proactively on occasion and possibly throw a warning if an active session is detected
https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_DescribeSessions.html