search

boto / boto3

AWS SDK for Python
https://aws.amazon.com/sdk-for-python/
Apache License 2.0
9.04k stars 1.87k forks source link

AWS IAM namespace discrepancy in boto3 vs. AWS API #1561

Closed jena3991 closed 6 years ago

jena3991 commented 6 years ago

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

session.get_available_services() ['acm', 'acm-pca', 'alexaforbusiness', 'apigateway', 'application-autoscaling', 'appstream', 'appsync', 'athena', 'autoscaling', 'autoscaling-plans', 'batch', 'budgets', 'ce', 'cloud9', 'clouddirectory', 'cloudformation', 'cloudfront', 'cloudhsm', 'cloudhsmv2', 'cloudsearch', 'cloudsearchdomain', 'cloudtrail', 'cloudwatch', 'codebuild', 'codecommit', 'codedeploy', 'codepipeline', 'codestar', 'cognito-identity', 'cognito-idp', 'cognito-sync', 'comprehend', 'config', 'connect', 'cur', 'datapipeline', 'dax', 'devicefarm', 'directconnect', 'discovery', 'dms', 'ds', 'dynamodb', 'dynamodbstreams', 'ec2', 'ecr', 'ecs', 'efs', 'elasticache', 'elasticbeanstalk', 'elastictranscoder', 'elb', 'elbv2', 'emr', 'es', 'events', 'firehose', 'fms', 'gamelift', 'glacier', 'glue', 'greengrass', 'guardduty', 'health', 'iam', 'importexport', 'inspector', 'iot', 'iot-data', 'iot-jobs-data', 'iotanalytics', 'kinesis', 'kinesis-video-archived-media', 'kinesis-video-media', 'kinesisanalytics', 'kinesisvideo', 'kms', 'lambda', 'lex-models', 'lex-runtime', 'lightsail', 'logs', 'machinelearning', 'marketplace-entitlement', 'marketplacecommerceanalytics', 'mediaconvert', 'medialive', 'mediapackage', 'mediastore', 'mediastore-data', 'meteringmarketplace', 'mgh', 'mobile', 'mq', 'mturk', 'opsworks', 'opsworkscm', 'organizations', 'pinpoint', 'polly', 'pricing', 'rds', 'redshift', 'rekognition', 'resource-groups', 'resourcegroupstaggingapi', 'route53', 'route53domains', 's3', 'sagemaker', 'sagemaker-runtime', 'sdb', 'secretsmanager', 'serverlessrepo', 'servicecatalog', 'servicediscovery', 'ses', 'shield', 'sms', 'snowball', 'sns', 'sqs', 'ssm', 'stepfunctions', 'storagegateway', 'sts', 'support', 'swf', 'transcribe', 'translate', 'waf', 'waf-regional', 'workdocs', 'workmail', 'workspaces', 'xray']

Request if the name space can be updated for boto3 library to match AWS API. Appreciate any help and response.

joguSD commented 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.