AWS Lambda Managed Instances with Java 25 and AWS SAM – Part 4 Monitoring, unsupported features, challenges and pricing

Introduction In part 1 of the series, we explained the ideas behind AWS Lambda Managed Instances and introduced our sample application. In part 2 , we explained what a Lambda Capacity Provider is and how to create it using AWS SAM. Part 3 was about how to create Lambda functions and attach them to a capacity provider. In this article, we’ll cover the following topics: monitoring, currently unsupported features, current challenges, and pricing. Capacity Provider Monitoring Capacity Provider provides various metrics. To see them, you can select the Capacity Provider by name and go to the “Monitoring” tab, or select the metrics from CloudWatch: The following metrics are provided: Capacity provider CPU utilization Capacity provider memory utilization Capacity provider allocated utilization Execution environment CPU utilization per function Execution environment memory utilization per function Execution environment count per function Capacity provider instance counts Unsupported Features Th