[ Bug Report ] I keep getting signed out of AWS as I'm working. ( Usually while editing Lambda functions ).

I understand your frustration with being repeatedly signed out of AWS while working, especially when editing Lambda functions. Unfortunately, there isn't a direct way to prevent automatic sign-outs entirely, as they are a security measure implemented by AWS. However, I can offer some insights and potential workarounds:

1. Session duration: AWS has default session timeouts for security reasons. If you're inactive for a certain period, you'll be automatically signed out.

2. Browser issues: Sometimes, browser settings or extensions can interfere with session management. Try using a different browser or disabling extensions to see if it helps.

3. Multiple tabs or windows: If you're working in multiple tabs or windows, make sure you're not inadvertently signing out in one, which could affect your session in others.

4. Network connectivity: Intermittent network issues can sometimes cause unexpected sign-outs. Ensure you have a stable internet connection.

5. IAM settings: If you're using an IAM user account, check with your AWS administrator about the session duration settings for your IAM role. They may be able to extend the session duration if it's set too short.

6. Use AWS CLI or SDK: For tasks like editing Lambda functions, consider using the AWS Command Line Interface (CLI) or Software Development Kit (SDK) instead of the web console. These tools often have more persistent authentication methods.

7. AWS CloudShell: This is a browser-based shell that comes pre-authenticated with your console credentials, which might help avoid frequent sign-outs when working with Lambda functions.

While these suggestions may not completely eliminate the issue, they might help reduce its frequency or provide alternative ways to work that are less affected by automatic sign-outs. If the problem persists, it may be worth contacting AWS Support for further assistance.
Sources
Sign out of AWS - AWS Sign-In

Have you checked the clock on your computer? If it is not correctly set you may find odd things happen because the authentication tokens are timestamped. If your clock is in the future or in the past it can cause issues.