Maintenance: change the maximum number of user-defined metric dimensions to 29

Summary

AWS increased the quotas for CloudWatch today; specifically, the maximum number of dimensions a metric can have was increased from 10 to 30 (https://aws.amazon.com/about-aws/whats-new/2022/08/amazon-cloudwatch-metrics-increases-throughput)

The validation should take this into account and raise the limit accordingly.

Why is this needed?

Previously, the limit was 10 dimensions per metric, and this was raised to 30 today. We should reflect it and allow the user to take advantage of this

Which area does this relate to?

No response

Solution

Change https://github.com/awslabs/aws-lambda-powertools-python/blob/bb1eda742583d58790219942a49a5d2489ea91ea/aws_lambda_powertools/metrics/base.py#L17 to MAX_DIMENSIONS = 29

Acknowledgment

• This request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

[leandrodamascena]

I don’t think this is a breaking change change either. The old code will continue to work with a maximum of 9 dimensions and the new one will be able to use a maximum of 29.

it’s a nice improvement to add more metrics/dimensions to Cloudwatch and I’m sure customers will be happy about it.

[leandrodamascena]

Hi @gshpychka. I think I can submit a PR for this issue if you’re busy. I think (not sure) that tomorrow there should be a release and it would be interesting to have this improvement.