Accessing policy object coming from Custom Authorizer output within a separate business logic Lambda

[keyurpd]

We have a separate custom lambda authorizer that validates incoming OIDC tokens and outputs a policy object with allow/deny, principal-id etc. Now we have a separate .net core business logic function that needs to read this principal-id and other custom outputs that the upstream authorizer might have sent.
Question: Is there a documentation and/or a sample where we can find how to read incoming context within the business logic Lambda?

aws-lambda-dotnet/Libraries/src/Amazon.Lambda.AspNetCoreServer/AbstractAspNetCoreFunction.cs

Line 446 in 8d61a2f

itemFeatures.Items[LAMBDA_CONTEXT] = lambdaContext;

[ashishdhingra]

Hi @keyurpd,

Good afternoon.

Thanks for posting the question. I'm not sure if I get the clear understanding of the question, following articles might be helpful (even though they don't document .NET specific example):

• Use AWS Lambda authorizers with a third-party identity provider to secure Amazon API Gateway REST APIs
• https://aws.amazon.com/blogs/compute/introducing-custom-authorizers-in-amazon-api-gateway/

Also refer Tutorial: Build and Test a Serverless Application with AWS Lambda . LambdaContext should be available when the API is called. If this is not what is required, would it be possible for you to share the code snippet of your Lambda function?

Thanks,
Ashish

[keyurpd]

LambdaContext should be available

Question is, how to access that when the downstream lambda is a .net core api? Following picture can help understand.

[ashishdhingra]

Hi @keyurpd,

LambdaContext should be available via this.HttpContext.Items["LambdaContext"] (Refer the below screenshot).

Please test at your end and confirm if this issue could be closed.

Thanks,
Ashish

[keyurpd]

This is good, thank you @ashishdhingra. It can be closed.
Though I also hope there were some samples/documentation available at the official site, language specific.

[ashishdhingra]

@keyurpd Thanks for confirming. I will make a note of identifying a place for documentation update. Closing this issue.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.