lambda extension cost for telemetry api

Question

I read
https://docs.aws.amazon.com/lambda/latest/dg/lambda-extensions.html
and in the article, it says "You are charged for the execution time that the extension consumes (in 1 ms increments). There is no cost to install your own extensions. For more pricing information for extensions, see AWS Lambda Pricing. For pricing information for partner extensions, see those partners' websites. See AWS Lambda extensions partners for a list of official partner extensions."

I can't find any specified per exetension execution time cost in AWS Lambda Pricing page.
how much does it cost?
I want to use lambda telemetry api for Elastic to send all my lambda logs to Elastic.

Uri · Accepted Answer

When you have an extension, it runs as part of the function execution environment. If your extension completes its task before the function completes, you pay nothing else. If your extension continues running after the function completes (which is usually the case with observability extensions), you pay for the additional time it takes the extension, using the regular Lambda duration cost.

re:Post Agent · Answer

When using Lambda extensions, including those that utilize the Lambda Telemetry API, the cost is integrated into the overall Lambda function execution pricing. There isn't a separate, specified cost for extension execution time on the AWS Lambda pricing page.

Instead, the pricing works as follows:

1. You pay for the combined compute time used to run your Lambda function code and all extensions, measured in 1-millisecond increments.

2. This combined time is added to your total Lambda execution duration and billed at the standard Lambda pricing rates, which vary based on the amount of memory allocated to your function.

3. For functions using the Telemetry API to send data to external services like Elastic, you might incur additional data transfer costs, which would be charged at Amazon EC2 data transfer rates.

When using the Lambda Telemetry API to send logs to Elastic, keep in mind:

1. The extension's execution time will be added to your function's duration, potentially increasing your Lambda costs.

2. Data transfer costs may apply when sending telemetry data out of AWS to Elastic, if it's hosted outside of AWS or in a different region.

3. There may be costs associated with storing and processing the data in Elastic, but these would be separate from AWS charges.

To manage costs effectively, monitor your Lambda function's performance metrics, especially the duration and memory usage. You can use CloudWatch to track these metrics and optimize your function and extension configurations accordingly. Additionally, consider using AWS Cost Explorer to analyze and forecast your Lambda-related expenses.  
**Sources**  
[Serverless Computing – AWS Lambda Pricing – Amazon Web Services](https://aws.amazon.com/lambda/pricing/)  
[Integrating the AWS Lambda Telemetry API with Prometheus and OpenSearch | AWS Open Source Blog](https://aws.amazon.com/blogs/opensource/integrating-the-aws-lambda-telemetry-api-with-prometheus-and-opensearch/)  
[Augment Lambda functions using Lambda extensions - AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/lambda-extensions.html)

lambda extension cost for telemetry api

Relevant content