which version of the AWS provider are you using? This sort of issue is usually caused by:
• the upstream provider not supporting the value
• the aws sdk not being updated to support the value
In any case, we can’t control this, it’s passed down to use