Controlling access in service-to-service communications with Cognito - Part 1

1

JSON Web Token

The access token is a JWT. If we inspect the token, we will see the required (and allowed) scopes there. The called service will validate if the required scopes are in the token.

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

2

Amazon Route 53

We can have our own domain too, which we must configure in Route 53. Custom domains also require a public certificate, which we can get free from ACM.

#Domain Name Registrar #Domain Names #Cloud Computing 44 social mentions

3

Amazon Cognito

Bob's solution starts with Amazon Cognito, which will generate the access tokens. The service that wants to access the other microservice will call Cognito and receive the token in the response (covered in this post).

#Identity Provider #SAML #Identity And Access Management 63 social mentions

4

AWS Certificate Manager

We can have our own domain too, which we must configure in Route 53. Custom domains also require a public certificate, which we can get free from ACM.

#Identity And Access Management #Network & Admin #Two Factor Authentication 23 social mentions

5

Amazon API Gateway

Next the service will make a request to the API of the other service with the token placed in the Authorization header.

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