Closed jena3991 closed 6 years ago
These naming discrepancies are deliberate and we won't be able to change them (the upstream services actually choose these). Also, I can't make any promises on when a service that is not currently in the SDK will become available.
Hello,
While programmatically validating the service names and I have ran into namespace discrepancy between boto3 and the AWS API. And few AWS Services also not available.
For example: boto3 <---> AWS
elb ---> elasticloadbalancing stepfunctions ---> states emr ---> elasticmapreduce NA automation NA aws-portal NA tag NA trustedadvisor
Request if the name space can be updated for boto3 library to match AWS API. Appreciate any help and response.