Public data access

The public authorization strategy grants everyone access to the API, which is protected behind the scenes with an API key. You can also override the authorization provider to use an unauthenticated IAM role from Cognito instead of an API key for public access.

Add public authorization rule using API key-based authentication

To grant everyone access, use the .public() authorization strategy. Behind the scenes, the API will be protected with an API key.

amplify/data/resource.ts
const schema = a.schema({
    .model({
      content: a.string(),
    .authorization(allow => [allow.publicApiKey()]),

In your application, you can perform CRUD operations against the model by specifying the apiKey auth mode.

  final todo = Todo(content: 'My new todo');
  final request = ModelMutations.create(
    todo,  
    authorizationMode: APIAuthorizationType.apiKey,
  final createdTodo = await Amplify.API.mutations(request: request).response;
  if (createdTodo == null) {
    safePrint('errors: ${response.errors}');
    return;
  safePrint('Mutation result: ${createdTodo.name}');
} on APIException catch (e) {
  safePrint('Failed to create todo', e);

Add public authorization rule using Amazon Cognito identity pool's unauthenticated role

You can also override the authorization provider. In the example below, identityPool 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.

amplify/data/resource.ts
const schema = a.schema({
    .model({
      content: a.string(),
    .authorization(allow => [allow.guest()]),

In your application, you can perform CRUD operations against the model using client.models.<model-name> with the identityPool auth mode.

If you're not using the auto-generated amplify_outputs.json file, then you must set the Amplify Library resource configuration's allowGuestAccess flag to true. This lets the Amplify Library use the unauthenticated role from your Cognito identity pool when your user isn't logged in.

Amplify configuration

src/App.tsx
import { Amplify } from "aws-amplify";
import outputs from "../amplify_outputs.json";
Amplify.configure(
    ...outputs,
    Auth: {
      Cognito: {
        identityPoolId: config.aws_cognito_identity_pool_id,
        userPoolClientId: config.aws_user_pools_web_client_id,
        userPoolId: config.aws_user_pools_id,
        allowGuestAccess: true,

src/App.tsx
import { generateClient } from 'aws-amplify/data';
import type { Schema } from '../amplify/data/resource'; // Path to your backend resource definition
const client = generateClient<Schema>();
const { errors, data: newTodo } = await client.models.Todo.create(
    content: 'My new todo',
    authMode: 'identityPool',

In your application, you can perform CRUD operations against the model with the iam auth mode.

  final todo = Todo(content: 'My new todo');
  final request = ModelMutations.create(
    todo,  
    authorizationMode: APIAuthorizationType.iam,
  final createdTodo = await Amplify.API.mutations(request: request).response;
  if (createdTodo == null) {
    safePrint('errors: ${response.errors}');
    return;
  safePrint('Mutation result: ${createdTodo.name}');
} on APIException catch (e) {
  safePrint('Failed to create todo', e);

Per-user/per-owner data access