The on-premises AWS integration for Port already supports ingestion of AWS Lambda tags as part of the resource metadata. However, this functionality is currently not available when using the AWS integration hosted by Port.
As a result, users leveraging the hosted integration are unable to see or utilize Lambda tags within Port, even though the same data is accessible via the AWS API and available through the self-hosted integration.
Proposed Enhancement
Extend the hosted AWS integration to include tag ingestion for AWS Lambda resources, matching the behavior of the on-prem version.
The integration should retrieve and store the Tags attribute for each Lambda function, making it accessible within the Port catalog.
Maintain consistency in structure and field naming with the existing implementation in the self-hosted version.