Pemberi Otorisasi API Gateway
Terapkan berbagai pemberi otorisasi API Gateway, termasuk pemberi otorisasi khusus Lambda dan pemberi otorisasi JWT, untuk autentikasi yang andal.
Pemberi Otorisasi API Gateway adalah pelajaran Serverless Backend with AWS Lambda & API Gateway gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Serverless Backend with AWS Lambda & API Gateway, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Serverless Backend with AWS Lambda & API Gateway mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
API Gateway Authorizers Intro
Welcome! In this lesson, we'll learn how to secure your serverless APIs using API Gateway Authorizers. These are crucial for controlling who can access your backend services.
Think of an authorizer as a security guard at the entrance of your API. Before any request reaches your Lambda function or other backend service, the authorizer checks the request's credentials.
Why Use API Gateway Authorizers?
Authorizers provide robust authentication and authorization for your APIs. Here's why they are essential:
- Protect Backend Resources: Prevent unauthorized access to your Lambda functions and other services.
- Decouple Auth Logic: Separate authentication logic from your main business logic, keeping your functions cleaner.
- Fine-Grained Access: Control access to specific API methods or resources based on user identity or roles.
Types of Authorizers
API Gateway offers several types of authorizers. Today, we'll focus on the two most flexible and commonly used:
- Lambda Custom Authorizers: A Lambda function you write to perform custom authentication.
- JWT Authorizers: API Gateway's native support for validating JSON Web Tokens (JWTs).
There's also IAM Authorizers, which use AWS IAM roles and policies, but we'll focus on the custom and JWT types here.
Lambda Custom Authorizers Explained
A Lambda Custom Authorizer is a Lambda function that you provide. API Gateway invokes this function with the incoming request's authorization token (e.g., from the Authorization header).
Your Lambda function then processes this token, performs its custom authentication logic (e.g., checks a database, calls an identity provider), and returns an IAM policy.
The Authorization Policy
The core output of your Lambda authorizer is an IAM policy document. This policy tells API Gateway whether to Allow or Deny the request to the target API endpoint.
It includes a principalId (the authenticated user's identifier) and a policyDocument specifying the permissions. If Allow, the request proceeds; if Deny, it's rejected with a 401 Unauthorized error.
Lambda Authorizer Code Example
Here's a simple Python Lambda function acting as an authorizer. It checks for a specific token and returns an 'Allow' or 'Deny' policy based on it.
Try changing the token in the test event to see different outputs!
def lambda_handler(event, context):
token = event.get('authorizationToken')
method_arn = event.get('methodArn')
if token == "my-secret-token-123":
# Allow access
return {
"principalId": "user123",
"policyDocument": {
"Version": "2012-10-17",
"Statement": [
{
"Action": "execute-api:Invoke",
"Effect": "Allow",
"Resource": method_arn
}
]
}
}
else:
# Deny access
return {
"principalId": "anonymous",
"policyDocument": {
"Version": "2012-10-17",
"Statement": [
{
"Action": "execute-api:Invoke",
"Effect": "Deny",
"Resource": method_arn
}
]
}
}
# --- Local Test (for demonstration) ---
if __name__ == "__main__":
print("Testing with 'my-secret-token-123':")
event_allow = {
"authorizationToken": "my-secret-token-123",
"methodArn": "arn:aws:execute-api:us-east-1:123456789012:/test/GET/items"
}
print(lambda_handler(event_allow, None))
print("\nTesting with 'invalid-token':")
event_deny = {
"authorizationToken": "invalid-token",
"methodArn": "arn:aws:execute-api:us-east-1:123456789012:/test/GET/items"
}
print(lambda_handler(event_deny, None))JWT Authorizers Explained
JWT (JSON Web Token) Authorizers allow API Gateway to natively validate JWTs. Instead of writing a Lambda function, you configure API Gateway with details about your JWT issuer.
When a request with a JWT comes in, API Gateway automatically performs validation steps like:
- Signature verification
- Expiration checks
- Audience and issuer validation
Configuring a JWT Authorizer
To set up a JWT authorizer, you typically provide API Gateway with:
- Issuer URL: The URL of the identity provider (e.g.,
https://cognito-idp.us-east-1.amazonaws.com/us-east-1_XXXXXXXfor Cognito). - Audience(s): A list of valid audiences for the token, ensuring the token is intended for your API.
- Identity Source: The header where the JWT is expected (e.g.,
$request.header.Authorization).
API Gateway then uses these details to fetch public keys and validate incoming JWTs.
When to Use Which Authorizer?
Choosing between Lambda and JWT authorizers depends on your needs:
- Lambda Authorizer: Use for highly custom authentication logic, integration with legacy systems, or identity providers not supporting standard OIDC/OAuth2. Offers maximum flexibility.
- JWT Authorizer: Ideal when using standard identity providers like AWS Cognito User Pools, Auth0, Okta, etc. It's simpler to set up and has less operational overhead.
For most modern applications using standard identity providers, JWT authorizers are often the preferred choice.
Authorizer Quick Check
Time for a quick check on what you've learned about API Gateway Authorizers!
Recap: Securing with Authorizers
You've now learned about API Gateway Authorizers, a vital component for securing your serverless APIs!
- Authorizers act as a front-door security check for your API endpoints.
- Lambda Custom Authorizers offer maximum flexibility for custom authentication logic.
- JWT Authorizers provide native, easy-to-configure validation for standard JSON Web Tokens.
By implementing authorizers, you ensure only legitimate requests access your backend services, enhancing the security of your applications.
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pemberi Otorisasi API Gateway” gratis?
Ya — teks lengkap “Pemberi Otorisasi API Gateway” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Serverless Backend with AWS Lambda & API Gateway, upgrade ke CoddyKit PRO. Kursus Serverless Backend with AWS Lambda & API Gateway mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Pemberi Otorisasi API Gateway”?
Terapkan berbagai pemberi otorisasi API Gateway, termasuk pemberi otorisasi khusus Lambda dan pemberi otorisasi JWT, untuk autentikasi yang andal. Kamu berlatih Serverless Backend with AWS Lambda & API Gateway dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Serverless Backend with AWS Lambda & API Gateway?
Tidak diperlukan pengalaman sebelumnya. Serverless Backend with AWS Lambda & API Gateway di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.
Berapa lama pelajaran “Pemberi Otorisasi API Gateway” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Serverless Backend with AWS Lambda & API Gateway ini?
Ya. Setiap pelajaran Serverless Backend with AWS Lambda & API Gateway menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Peran dan Izin IAM
- Pemberi Otorisasi API Gateway
- Mengamankan Lambda dengan VPC
- Melindungi Rahasia dengan AWS Secrets Manager