- Le plus récent
- Le plus de votes
- La plupart des commentaires
As to documentation, tags cannot be applied to Lambda@Edge resources, which I take it to be that tags are not applicable once Lambda@Edge functions are deployed. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-requirements-limits.html#lambda-requirements-tagging
The only viable way to show cost per Lamba@Edge function is to use Cost and Usage Report, with query like below. Please note that both Lambda-Edge-GB-Second and Lambda-Edge-Request usage types are included. ` SELECT line_item_resource_id as Resource, SUM(CAST(line_item_unblended_cost AS decimal(16,8))) AS TotalSpend FROM
<table name> WHERE (year='2021') AND (month='01') AND line_item_product_code = 'AmazonCloudFront' AND line_item_usage_type LIKE '%Lambda-Edge%' AND line_item_line_item_type = 'Usage' GROUP BY line_item_resource_id ORDER By TotalSpend DESC; `I would also remind that you need to consider CloudWatch log cost for Lambda@Edge function as well, which you would have to use CUR to analyze cost per log group for each function.
Contenus pertinents
- demandé il y a un an
- demandé il y a 6 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- Comment résoudre les erreurs 500, 502 et 503 causées par les fonctions Lambda@Edge dans CloudFront ?AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an