Error launching aws-shell in Cygwin on windows 10

Works fine in cmd window. Using python 3.6.5. Launched cygwin as admin. Pip'ed installed and upgraded aws and aws-shell.
Ran aws-shell and got the following:

$ aws-shell
Creating doc index in the background. It will be a few minutes before all documentation is available.
Traceback (most recent call last):
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\runpy.py", line 85, in _run_code
exec(code, run_globals)
File "C:\Users\lupee\AppData\Local\Programs\Python\Python36-32\Scripts\aws-shell.exe\__main__.py", line 9, in
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\site-packages\awsshell\__init__.py", line 70, in main
shell.run()
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\site-packages\awsshell\app.py", line 292, in run
document = self.cli.run(reset_current_buffer=True)
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\site-packages\awsshell\app.py", line 285, in cli
self._cli = self.create_cli_interface(self.show_completion_columns)
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\site-packages\awsshell\app.py", line 487, in create_cli_interface
input=self._input, output=self._output)
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\site-packages\prompt_toolkit\interface.py", line 80, in __init__
self.output = output or create_output()
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\site-packages\prompt_toolkit\shortcuts.py", line 118, in create_output
return Win32Output(stdout)
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\site-packages\prompt_toolkit\terminal\win32_output.py", line 80, in __init__
info = self.get_win32_screen_buffer_info()
File "c:\users\lupee\appdata\local\programs\python\python36-32\lib\site-packages\prompt_toolkit\terminal\win32_output.py", line 172, in get_win32_screen_buffer_info
raise NoConsoleScreenBufferError
prompt_toolkit.terminal.win32_output.NoConsoleScreenBufferError: Found xterm, while expecting a Windows console. Maybe try to run this program using "winpty" or run it in cmd.exe instead. Or otherwise, in case of Cygwin, use the Python executable that is compiled for Cygwin.

Thx
Lew

Reproduce the `aws-shell` launch in Cygwin on Windows with the reported Python setup, then inspect `awsshell/app.py` around `create_cli_interface`, where the traceback reaches prompt_toolkit. Done means determining the cause of `NoConsoleScreenBufferError` and establishing the supported behavior for this environment.

Written by the indexing model from the issue text.