Controlling access to IAM-protected API endpoints with Cognito groups

1

AWS Lambda

I discussed a way to control access to endpoints using JSON web tokens and a Lambda authorizer earlier.

#Cloud Computing #Cloud Hosting #Backend As A Service 244 social mentions

2

AWS Identity and Access Management

Each group will have an IAM role assigned. The roles will allow read/write and read access to the members of the FullAccess and ReadOnlyAccess groups, respectively.

#Identity And Access Management #Identity Provider #SSO 52 social mentions

3

AWS ElasticWolf Client Console

When we call an AWS service API endpoint (e.g., API Gateway Invoke, SNS Publish or S3 CreateBucket), we must sign the request using Signature Version 4. The SDKs and the CLI will automatically do it on behalf of us using the credentials we provide. But when we protect a public API endpoint with IAM, we should build the logic to sign the request in the code.

#Developer Tools #Weather Apps #Weather API 18 social mentions

4

Amazon API Gateway

In this scenario we protect the backend compute resources with an HTTP API type of API Gateway. We'll set up IAM authorization at each route, which eliminates the need for tokens and custom authorizers. It's also the safest way to protect an endpoint since it delegates the authorization task to the robust IAM service.

#API Tools #APIs #Web Service Automation 94 social mentions

5

AWS Mobile Services

We can use the Signer class Amplify provides in a React front-end application to sign the API requests whose targets are various the API Gateway endpoints.

#Developer Tools #Realtime Backend / API #App Development 77 social mentions