awslabs / awslabs/agentcore-samples
02-use-cases - [Multi-tenant content filtering at row-level based on logged in user]
- Dominant language
- Python
- Stars
- 3.4k
- Forks
- 1.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 30
Description
**Please list the sample in which the bug is present.**
I need a mechanism to determine who the logged in user is and have a row-level access control on the data ingested.
```
02-use-cases/...
```
Enterprises would like to create customer facing AI agents but are concerned with the agents inadvertently exposing data that users do not have access to. To resolve this enterprises have to create additional filtering and mapping on into their applications to determine who the logged in user is.
**Improvement Description**
This solution automatically infers the logged in user based on oauth identity providers like cognito. Enterprises can plug in their existing federated user identity providers and let the Agentcore gateway and interceptors take care of translating to the calling user and ensuring data is filtered based on the end user.
```
Please fill information here.
```
Contributor guide
Assessment
This issue has not been assessed yet.