Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Name:
interface
Value:
Amplify has re-imagined the way frontend developers build fullstack applications. Develop and deploy without the hassle.

Page updated Mar 5, 2025

Use existing AWS resources

Existing Amazon API Gateway resources can be used with the Amplify Libraries by referencing your API Gateway endpoint and configuring authorization in your amplifyconfiguration.json file.

{
"api": {
"plugins": {
"awsAPIPlugin": {
"[API NAME]": {
"endpointType": "REST",
"endpoint": "[API GATEWAY ENDPOINT]",
"region": "[REGION]",
"authorizationType": "[AUTHORIZATION TYPE]",
...
}
}
}
}
}
  • API NAME: Friendly name for the API (e.g., api)
    • endpoint: The HTTPS endpoint of the API (e.g. https://aaaaaaaaaa.execute-api.us-east-1.amazonaws.com/api)
    • region: AWS Region where the resources are provisioned (e.g. us-east-1)
    • authorizationType: Authorization mode for accessing the API. This can be one of: NONE, AWS_IAM, AMAZON_COGNITO_USER_POOLS, or API_KEY. Each mode with the exception of NONE requires additional configuration parameters. See Configure authorization modes for details.

Note that before you can add an AWS resource to your application, the application must have the Amplify libraries installed. If you need to perform this step, see Install Amplify Libraries.