Page updated Jan 16, 2024

Define authorization rules

Amplify Flutter v0 is now in Maintenance Mode until July 19th, 2024. This means that we will continue to include updates to ensure compatibility with backend services and security. No new features will be introduced in v0.

Please use the latest version (v1) of Amplify Flutter to get started.

If you are currently using v0, follow these instructions to upgrade to v1.

When determining the authorization mode for your REST endpoint, there are a few built in options and customizations you can use.

IAM Authorization

By default, the API will be using IAM authorization and the requests will be signed for you automatically. IAM authorization has two modes: one using an unauthenticated role, and one using an authenticated role. When the user has not signed in through Amplify.Auth.signIn, the unauthenticated role is used by default. Once the user has signed in, the authenticate role is used, instead.

When you created your REST API with the Amplify CLI, you were asked if you wanted to restrict access. If you selected no, then the unauthenticated role will have access to the API. If you selected yes, you would have configured more fine grain access to your API.

Unauthenticated Requests

You can use the API category to access API Gateway endpoints that don't require authentication. In this case, you need to allow unauthenticated identities in your Amazon Cognito Identity Pool settings. For more information, please see the Amazon Cognito developer documentation.

When your API is configured to use IAM as the authorization type, your requests will automatically have IAM credentials added to the headers of outgoing requests. You can verify that IAM is being used as the authorization type by inspecting the authorizationType associated with your API in amplifyconfiguration.dart:

2 "awsAPIPlugin": {
4 "endpointType": "REST",
5 "endpoint": "YOUR-REST-ENDPOINT",
6 "region": "us-west-2",
7 "authorizationType": "AWS_IAM"
8 }
9 }


If you want to configure a public REST API, you can set an API key in Amazon API Gateway. Then, update your amplifyconfiguration.dart to reference it. The value associated to the "authorizationType" key should be "API_KEY". Also include an "API_KEY" as a key, and set its value to whatever your configured in API Gateway.

2 "awsAPIPlugin": {
4 "endpointType": "REST",
5 "endpoint": "YOUR-REST-ENDPOINT",
6 "region": "us-west-2",
7 "authorizationType": "API_KEY",
8 "apiKey": "YOUR_API_KEY"
9 }
10 }

Cognito User pool authorization

If you set up the API Gateway with a custom authorization with a Cognito User pool, then you can set the amplifyconfiguration.dart to use AMAZON_COGNITO_USER_POOLS .

2 "awsAPIPlugin": {
4 "endpointType": "REST",
5 "endpoint": "YOUR-REST-ENDPOINT",
6 "region": "us-west-2",
7 "authorizationType": "AMAZON_COGNITO_USER_POOLS"
8 }
9 }

Your amplifyconfiguration.dart should contain Cognito configuration in the awsCognitoAuthPlugin block, including details about your Cognito user pool:

2 "CognitoUserPool": {
3 "Default": {
4 "PoolId": "YOUR-POOL-ID",
5 "AppClientId": "YOUR-APP-CLIENT-ID",
6 "AppClientSecret": "YOUR-APP-CLIENT-SECRET",
7 "Region": "us-east-1"
8 }
9 },
10 "CredentialsProvider": {
11 "CognitoIdentity": {
12 "Default": {
14 "Region": "us-east-1"
15 }
16 }
17 }

With this configuration, your access token will automatically be included in outbound requests to your API, as an Authorization header. For more details on how to configure the API Gateway with the custom authorization, see this


To start, create a provider class inheriting from OIDCAuthProvider.

1import 'package:amplify_api/amplify_api.dart';
3class CustomOIDCProvider extends OIDCAuthProvider {
4 const CustomOIDCProvider();
7 Future<String?> getLatestAuthToken() async => '[OPEN-ID-CONNECT-TOKEN]';

Then, include it, along with any other auth providers, in the call to addPlugin.

1await Amplify.addPlugin(AmplifyAPI(
2 authProviders: const [
3 CustomOIDCProvider(),
4 CustomFunctionProvider(),
5 ],

Note: When using custom auth providers, getLatestAuthToken must be called before every API call, so it's important to minimize the amount of work this method performs. Consider caching your token in-memory so that it's available synchronously to the plugin, and only refresh it when necessary.

Customizing HTTP request headers

To use custom headers on your HTTP request, you need to add these to Amazon API Gateway first. For more info about configuring headers, please visit Amazon API Gateway Developer Guide

If you used the Amplify CLI to create your API, you can enable custom headers by following these steps:

  1. Visit Amazon API Gateway console.
  2. In the Amazon API Gateway console, click on the path you want to configure (e.g. /{proxy+})
  3. Click the Actions dropdown menu and select Enable CORS
  4. Add your custom header (e.g. my-custom-header) on the text field Access-Control-Allow-Headers, separated by commas, like: 'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token,my-custom-header'.
  5. Click on 'Enable CORS and replace existing CORS headers' and confirm.
  6. Finally, similar to step 3, click the Actions drop-down menu and then select Deploy API. Select Development on deployment stage and then Deploy. (Deployment could take a couple of minutes).