No Option to filter attributes based on Regex Match in Cognito

[zubairzahoor]

I need to get a list of emails that end with a particular domain(s) from Cognito by using cognito.listUsers({}).
Right now I can only either provide the filter type for an exact match using = or for a prefix match using ^= which is extremely limited to say the least.
I (along with possibly many other developers) would like to have the ability to list users from cognito based on a match with a regex pattern.
Or have a options like 'contains', 'not contains', 'ends with', 'exists' and more like these to be able to list the users we exactly want.

Right now, I have to retrieve each and every user in Cognito User Pool using Pagination and then filter them based on what I need which of course is no good when the total number of Users goes in thousands (given there is a limit of 60 users per page and a rate limit on number of requests)

[github-actions]

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

[kellermartin13]

Following up on this - I would also like the ability to filter by regex.

[Channeas]

+1 Filtering with regex would be extremely useful

[s-stefanov]

+1

[jmcouch]

+1
it is unfortunate this was closed, would be extremely useful

[eceramanan]

+1 Filtering with regex would be extremely useful

[ghost]

+1
Even if not Regex, more options like contains() or endswith() would be a welcomed addition.

[clovisj]

+1

[npkumaroyo]

+1

[dsilva342]

+1

[john-at-mc]

+1

[kennedysam97]

+1

[evanmcarlson]

@ajredniwja @awstools please review this issue; the ability to only query a prefix is not helpful.

[GaiAshkenazyVia]

+1

[roniceyemeli]

+1, please open this issue again

[mibrennan]

+1, would love this

[Beni312]

+1, i need this

[mmandviwala]

+1

[ed100miles]

+1

[pranavacharyafdb]

+1

[AntonioLuisME]

3.5 years on and still no response.

I don't understand why there are filter restrictions in the first place. It seems like such a miss to not allow contains() type search from the get go. It really limits the apps that can be built using AWS pool data unless of course you build your own archaic workarounds.

As for devs reading, I'd recommend stop using a service that does not serve or listen to our needs.

[felipeabou]

+++++++++++++++++++++++++1

[kmartin-bh]

I've long since abandoned cognito. Far too restrictive. I do love getting emails from this thread every few months 🙃

[AntShep]

+1 like others :)

[RanVaknin]

Hello everyone on this thread.

Thank you for your patience. We had to dig this issue up from the old JS SDK v2 repo that is going into maintenance mode. We apologize for not seeing this sooner. We now have better tools that help detect languishing issues of this sort, so hopefully we can minimize these sorts of scenarios where issues get unnoticed going forward.

To be clear, this feature request is intended for the Cognito service itself, and not the SDK team. The ask to add regex based service-side filtering is an API enhancement. Since the AWS SDKs are code generated from the API of the various AWS services, the SDK team cannot add this filtering functionality, especially because this needs to be supported with the service itself first.

I have upstreamed this feature request to the Cognito team directly (internal ticket #P145422926). Our team does not have visibility as to when / if this is going to be implemented, all we can do is advocate on your behalf and make sure this is seen by the right people.

If any of the 36+ participants on this thread has access to AWS support via the AWS console, I highly encourage you to open a support ticket and reference the ticket ID mentioned above.

Since this is not directly actionable by the SDK team, once we hear back from the service team I will provide an update and close this issue.

Thanks again for all of the engagement,
Ran~

[github-actions]

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.