MWAA - / in users

[bob-skowron]

Bringing this to a top level issue. As jaklan noted below, any thoughts on how we could manage users in MWAA given this limitation? I've also reached out to AWS to get their thoughts.

Thanks!

          Sorry for bumping the old issue, but maybe you have a quick answer for that - AWS [added support for REST API in MWAA](https://aws.amazon.com/blogs/big-data/introducing-amazon-mwaa-support-for-the-airflow-rest-api-and-web-server-auto-scaling/), but the problem is - usernames in MWAA start with `assumed-role/` prefix, so they contain slash.

Is there any way to use /users endpoints not to receive The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again. error?

Neither /users/assumed-role/foobar nor /users/assumed-role%2Ffoobar seems to work.

Originally posted by @jaklan in #20063 (comment)

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[eladkal]

The issue is not a bug in the open source but a problem with MWAA. I notified the MWAA team about your report but I suggest you will also contact the AWS support directly they might provide more information.

Closing as not open source bug.

[eladkal]

I see MWAA already has open issue for it in thier docker image
aws/amazon-mwaa-docker-images#127