Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for AWS API Gateway with Lambda proxy integration #357

Open
au-phiware opened this issue Jun 7, 2023 · 1 comment
Open

Support for AWS API Gateway with Lambda proxy integration #357

au-phiware opened this issue Jun 7, 2023 · 1 comment

Comments

@au-phiware
Copy link

I'm looking to contribute an integration between AWS API Gateway and APIClarity using a Lambda proxy integration as a POC. My initial thoughts is to build a proxy that converts the input and output formats of AWS API Gateway into the schema of the plugin API.

Are you aware of any prior work that uses APIClarity in an AWS environment (outside of k8s)?

@jubarbot-cisco
Copy link
Contributor

Hi @au-phiware,
Thank you for reaching out !
Your idea makes perfect sense. I'm not aware of any work about using AWS lambdas to push traces to APIClarity.

Keep in mind that the Trace Source (Kong gateway, istio proxy, AWS lambda) can be running in one environment, and APIClarity in another.

APIClarity can also run on you local machine (no Kubernetes involved) or inside a virtual machine, running in AWS, as long as the Trace Source can send traces to APIClarity.
The only thing that you will miss, is the BFLA (Broken Function Level Authorization) feature which relies on the K8S API.

Feel free to contribute, we will be more than happy to help you.

Thank you !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants