Page updated Nov 20, 2023

Signed-in user data access

The private authorization strategy restricts record access to only signed-in users authenticated through IAM, Cognito, or OpenID Connect, applying the authorization rule to all users. It provides a simple way to make data private to all authenticated users.

Add signed-in user authorization rule

You can use the private authorization strategy to restrict a record's access to every signed-in user.

Note: If you want to restrict a record's access to a specific user, see Per-user/per-owner data access. The private authorization strategy detailed on this page applies the authorization rule for data access to every signed-in user.

In the example below, anyone with a valid JWT token from the Cognito user pool is allowed access to all Todos.

export const schema = a.schema({ Todo: a.model({ content: a.string() }).authorization([ a.allow.private() ]) })
1export const schema = a.schema({
2 Todo: a.model({
3 content: a.string()
4 }).authorization([
5 a.allow.private()
6 ])
7})

Override the authentication provider

You can also override the authorization provider. In the example below, iam is specified as the provider which allows you to use an "Unauthenticated Role" from the Cognito identity pool for public access instead of an API key. Your Auth resources defined in amplify/auth/resource.ts generates scoped down IAM policies for the "Unauthenticated role" in the Cognito identity pool automatically.

export const schema = a.schema({ Todo: a.model({ content: a.string() }).authorization([ a.allow.private("iam") ]) })
1export const schema = a.schema({
2 Todo: a.model({
3 content: a.string()
4 }).authorization([
5 a.allow.private("iam")
6 ])
7})

In addition, you can also use OpenID Connect with private authorization. See OpenID Connect as an authorization provider.