You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)?
The text was updated successfully, but these errors were encountered:
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.
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)?
The text was updated successfully, but these errors were encountered: