1 Answer
- Newest
- Most votes
- Most comments
0
I have also got same error. Apparently this is bug from AWS side, raised a Ticket to AWS support and they increased the limit from backend. Below is the response from AWS Support:
"We have reset the value for "max-interactive-sessions" from 0 to the default which is 100. Unfortunately this value recently got changed due to a bug on the AWS side"
answered 2 years ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago