Difference between revisions of "AWS API Gateway authorization and access control"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | To control how clients call an [[RESTful API]], use [[IAM]] permissions, a [[Lambda]] authorizer, or an [[Amazon Cognito]] user pool. | + | To control how clients call an [[RESTful API]], use [[AWS Identity and Access Management|IAM]] permissions, a [[Lambda]] authorizer, or an [[Amazon Cognito]] user pool. |
Revision as of 15:58, 11 July 2021
To control how clients call an RESTful API, use IAM permissions, a Lambda authorizer, or an Amazon Cognito user pool.
See also
- API, Redfish (specification), GRPC, RESTful, FastAPI, AWS API Gateway Service, OpenAPI, GraphQL, Protocol Buffers, Google APIs Explorer, Zapier, Postman, Full Life Cycle API Management, GSSAPI, Apilayer, Amazon API Gateway, Apigee, API as a Service (APIaaS), Crypto API
- AWS, Amazon Managed Services, AWS Management & Governance, computing, security, networking, AWS compliance, AWS Outposts AWS Free Tier, AWS certifications, AWS Trusted Advisor, AWS Systems Manager, AWS Config, IAM Access Analyzer, AWS Cost Explorer, AWS Cost Management, AWS Budgets, AWS Organizations, AWS dev: (CodeStar, Cloud9), AWS Partner Network (APN), AWS Resource Access Manager, AWS Quick Starts, AWS Global Accelerator, AWS Elemental MediaStore, AWS Enterprise support, AWS support, AWS Professional Services Consultants, AWS Cloud Map, AWS Marketplace, AWS CLI, AWS Management Console, AWS acceptable use policy, amazonaws.com, Quotas, AWS Support plans, AWS Resource Explorer, AWS Managed Services (AMS), AWS savings, AWS Nitro System, AWS Activate, Serverless, AWS timeline
Advertising:
