Govern every AWS Cognito OAuth client from one dashboard.
Taco connects to AWS Cognito to inventory OAuth and OpenID Connect clients, validate new client requests, control scopes and audiences, and keep an audit trail of every change.
Your AWS Cognito tenant has more OAuth clients than anyone can explain.
Every team registers its own apps. Redirect URIs drift, secrets are never rotated, and nobody remembers who owns the client with full API access. Taco brings order to AWS Cognito client management without changing how tokens are issued.
Who owns this AWS Cognito client?
Taco builds an inventory of every OAuth and OpenID Connect client in AWS Cognito, with owners, environments, and custom metadata your team can actually search.
Anyone with console access can create a client.
Route new AWS Cognito client requests through validation and approval. Grant types, redirect URIs, and scopes are checked against your policies before the client exists.
This client should not have access to that API.
Review and restrict scopes and audiences per client, and see at a glance which applications can call your most sensitive APIs.
AWS Cognito OAuth clients
A governance layer for your AWS Cognito clients.
Taco connects to the AWS Cognito admin APIs and manages OAuth and OpenID Connect clients on your behalf: creation, updates, approvals, and reviews.
AWS Cognito keeps issuing tokens and running your authorization flows. Taco makes sure the clients it serves are the ones you actually approved.
Nothing to migrate
Existing AWS Cognito clients are imported as-is. Your apps keep their client IDs and flows.
Policy before creation
Grant types, redirect URIs, and scopes are validated before a client reaches AWS Cognito.
Full traceability
Every client change, approval, and secret rotation is recorded with who did it.
Connect your AWS Cognito environment
Give Taco admin API credentials for each AWS Cognito environment you want to govern.
Import and tag existing clients
Assign owners, environments, and metadata to the clients already registered in AWS Cognito.
Enforce your client policies
New clients and changes go through validation and approval before they are applied in AWS Cognito.
Best for IAM and platform teams running AWS Cognito across several teams or environments who need to know which clients exist and why.
Every AWS Cognito client. Known, owned, and approved.
Taco sits next to AWS Cognito, not in front of it. Token issuance stays untouched โ Taco manages the client configuration that AWS Cognito relies on.
๐๏ธ
One inventory for all your AWS Cognito clients.
See every OAuth and OpenID Connect client registered in AWS Cognito, across environments, with its owner, grant types, and last change. Add custom metadata so the inventory reflects how your organization works.
billing-web
authorization_code ยท owner: payments
reporting-batch
client_credentials ยท owner: data
test-app-2
implicit ยท owner: unknown
โ
Validate clients before they reach AWS Cognito.
Teams request clients through Taco. Grant types, redirect URIs, and requested scopes are checked against your policies, and sensitive requests go to the right approver before anything is created in AWS Cognito.
๐ก๏ธ
A clear history for every client change.
Creations, scope changes, secret rotations, and approvals are logged with the requester and the approver. When a security review asks why a client can call an API, you have the answer.
Ready to get started?
Taco connects to AWS Cognito to inventory OAuth and OpenID Connect clients, validate new client requests, control scopes and audiences, and keep an audit trail of every change.
Contact Us