1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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"
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr