support-tools | For support tools to be | Development Tools library

I am having trouble trying to set up a lambda authorizations for a WebSocket API.

Serverless.yml

I have the following scenario:

1 - A Web Client App authenticates an user throught a Cognito User pool

2 - A Web Client App retrieves a credentials provided by the Cognito Identity Pool (STS temporary credentials, not the id token or acess token)

3 - Web Client App sends the above credentials to the API Gateway which is set to use AWS_IAM as Authorization method

4 - The API Gateway invokes a lambda function which need to know who is the user associated to the credentials: user id or username

The problem

How retrieve the user's data from a credential provided by the Cognito Identity Pool in the API Gateway or in the lambda function?

My first idea was to send the id token in a additional HTTP header to the API Gateway, but I didn't find a way to decode the token in API Gateway.

The second alternative was the id token pass through to the function lambda that would decode the token, but I think it would be an heaveweight operation to a lambda function.

I am doing king of transfer learning. What I have done is First train the model with the big datasets and save the weights. Then I train the model with my dataset by freezing the layers. But I see there was some overfitting. So I try to change the dropout of the model and load the weights since the numbers are changing while drop out are changing. I find difficulties to change the dropout.

Directly my question is, Is it possible to change the model's dropout while loading the weights?

my scenario 1 is like that

1. model defined.
2. train the model.
3. list item
4. save weights.

5. ...

6. redefine the dropout others are not changed in the model

7. load the weights . I got the error.

2nd Scenario

1. model1 defined.

2. train the model.

3. save weights

4. load model1 weights to model1

5. ....

6. model2 defined by changing the dropouts.

7. try to set the wights of model1 to model 2 using for loop except for the dropout layer. I got an error.

This is the error I got.

I am trying to create APIs using API gateway and Lambda functions.

Based on the user group ( not the Cognito user groups ), I want to provide access to separate DynamoDB tables.

The approach I am following is, I am creating a separate Cognito user pool for every group of users.

When the user logs in, he is authenticated with the appropriate user pool.

For calling the subsequent APIs, I am planning to make use of Lambda authorizer.

The user will pass the ID token in the HTTP header request and I want to validate this ID token.

Is this the right approach? Or if there is any better approach for implementing this workflow.

Can we make use of Cognito user groups and will it be a secure approach?

I want to strictly separate the tables of one user group from another.

I came across the below link, to verify the ID token.

https://github.com/awslabs/aws-support-tools/blob/master/Cognito/decode-verify-jwt/decode-verify-jwt.js

Im Using User Pool, and is possible develop a api to communicate with AWS Cognito? or just to communicate with front-end apps (android, ios, javascript web)?

And if is possible, how can I identify the user logged and get their informations?

UPDATE 1: To get decode jwt informations: https://github.com/awslabs/aws-support-tools/tree/master/Cognito/decode-verify-jwt

UPDATE 2: Cognito is better to use on front-end, because you need store 'cognitoUser' object. And the methods is using this object.

UPDATE 3: You can do the login on backend, and use the token to use API Gateway on AWS. But the problem is if you need update something on Cognito. If you need, you can use the admin methods (https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/Welcome.html).

I believe I am missing something with the implicit grant process and access tokens in aws cognito.

To this point:

1. Have a user pool, with a client app configured for implicit flow and scopes openid, profile, aws.cognito.signin.user.admin

2. Used a stack overview and the official documentation and older white papers to achieve:

3. Login process that redirects to aws cognito UI, and back to my app, with tokens and other information in the fragment portion of the URL.

4. The access_token value parses at jwt.io and signature checks out using the aws jwt tool

Problem:

The recommended step is to "verify that the access token belongs to us" through the tokeninfo api call. When I attempt to call tokeninfo via javascript code and testing via postman (using: https://api.amazon.com/auth/o2/tokeninfo?access_token=eyJraWQiOiJoVFBa... )

I get the result:

I am trying to make a node express app where I fetch data from different url's making a call to node-fetch to pull the body of some pages and other information about certain url endpoints. I want to then render a html table to display this data through an array of information. I am having trouble with the call to render the information as all the functions are asynchronous making it difficult to make sure all the promise calls have been resolved before making my call to render the page. I have been looking into using bluebird and other promise calls of .finally() and .all() but they don't seem to work on my data as it is not an array of promise calls, but an array of objects. Each object was 4 promise calls to fetch data relating to a column of my table all in one row. Is there a function or specific way to render the page after all promises are resolved?