Implement AWS Security Best Practices in APIGEE - Lambda Integrations

For connecting from APIGEE to AWS Lambda, there are primarily two ways.
1) Using Google created AWS Lambda Extension
2) NodeJS Hosted Target Proxy Type

Both the proxy types are using "AWS API Key" as authentication mechanism. AWS discourages use of API KEY; encourages API KEY rotation and temporary credentials instead of long term credentials as security best practices.

"AWS Instance Profile Policy" implements these best practices behind the scenes. Can this mechanism be used in above APIGEE-AWSLambda integration scenarios ?

Will "AWS Lambda Extension" and "Hosted Target" model support this credential mechanism?

0 0 474
0 REPLIES 0