Examples of using Lambda authorizer in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
Create an API Gateway Lambda Authorizer Lambda Function.
The next procedure shows how to configure an API method to use the Lambda authorizer.
Create a Lambda Function for a Lambda Authorizer of the TOKEN type.
In Name, type a header name that matches the TokenSource name you specified when you created the Lambda authorizer for the API.
Configure Cross-Account Lambda Authorizer Using the API Gateway Console.
The stringified value of the specified key-value pair of thecontext map returned from an API Gateway Lambda authorizer Lambda function.
You must have created a Lambda authorizer to have this choice displayed in the drop-down menu.
Set up API methods to require an API key and enable the Lambda authorizer on the methods as well.
The response shows that the API Gateway Lambda authorizer returns a 403 Forbidden response without authorizing the call to access the HTTP endpoint.
After you create the Lambda function and verify that it works,use the following steps to configure the API Gateway Lambda authorizer(formerly known as the custom authorizer) in the API Gateway console.
An Amazon API Gateway Lambda authorizer(formerly known as a custom authorizer) is a Lambda function that you provide to control access to your API methods.
You can do this by using IAM permissions, a Lambda authorizer, or an Amazon Cognito user pool.
Having configured the Lambda authorizer(formerly known as the custom authorizer) and deployed the API, you should test the API with the Lambda authorizer enabled.
When a client calls your API,API Gateway verifies whether a Lambda authorizer is configured for the API method.
Before creating an API Gateway Lambda authorizer, you must first create the AWS Lambda function that implements the logic to authorize and, if necessary, to authenticate the caller.
To control how clients call an API,use IAM permissions, a Lambda authorizer, or an Amazon Cognito user pool.
To use the IAM permissions, a Lambda authorizer, or an Amazon Cognito user pool to authenticate the caller, set the authorization-type to AWS_IAM, CUSTOM, or COGNITO_USER_POOLS, respectively.
The next two sectionsexplain the Input to an Amazon API Gateway Lambda Authorizer and Output from an Amazon API Gateway Lambda Authorizer. .
For a Lambda authorizer(formerly known as a custom authorizer) of the TOKEN type, you must specify a custom header as the Token Source when you configure the authorizer for your API.
For information on how to create a Lambda authorizer, see Use API Gateway Lambda Authorizers.
To grant another AWS acccount permission to call authorizer: create or create-authorizer to control the Lambda function used in your Lambda authorizer, you can create the following IAM policy.
When creating the Lambda function for your API Gateway Lambda authorizer, you assign an execution role for the Lambda function if it calls other AWS services.
For the Lambda proxy integration,API Gateway passes the context object from a Lambda authorizer directly to the backend Lambda function as part of the input event.
The response shows that the API Gateway Lambda authorizer returns a 200 OK response and successfully authorizes the call to access the HTTP endpoint(http://httpbin. org/get) integrated with the method.
To permit only authenticated users to call the method,you can use IAM roles and policies, a Lambda authorizer(formerly known as a custom authorizer), or an Amazon Cognito user pool.
For more information, see Configure Cross-Account Lambda Authorizer Using the API Gateway Console and Build an API Gateway API with Cross-Account Lambda Proxy Integration.