Na}{

File Content: helptext.pyc

�
=��Xc�����������@���sP��d��d�l��m�Z�d��d�l��m�Z�d�Z�d�Z�d�Z�d�Z�d�Z�d�Z�d	�e�d
�e�d�Z	�d�Z
�d
�e�d�e�d�Z�d�Z�d�Z
�d�Z�d�Z�d�Z�d�Z�d�Z�d�Z�d�e�d�e�d�Z�d�Z�d�Z�d�Z�d�Z�d�Z�d �Z�d!�Z�d"�Z�d#�Z�d$�Z�d%�Z�d&�Z �d'�Z!�d(�Z"�d)�Z#�d*�Z$�d+�Z%�d,�Z&�d-�Z'�d.�Z(�d/�Z)�d0�Z*�d1�Z+�d2�Z,�d3�S(4���i����(���t
���EMR_ROLE_NAME(���t
���EC2_ROLE_NAMEs���Shuts down a list of clusters. When a cluster is shut down, any step not yet completed is canceled and the Amazon EC2 instances in the cluster are terminated. Any log files not already saved are uploaded to Amazon S3 if a LogUri was specified when the cluster was created. 'terminate-clusters' is asynchronous. Depending on the configuration of the cluster, it may take from 5 to 20 minutes for the cluster to completely terminate and release allocated resources such as Amazon EC2 instances.s����A unique string that identifies the cluster. This identifier is returned by <code>create-cluster</code> and can also be obtained from <code>list-clusters</code>.s9��Amazon S3 location of the Hbase backup. Example:<code>s3://mybucket/mybackup</code> where mybucket is the specified Amazon S3 bucket and mybackup is the specified backup location. The path argument must begin with s3:// in order to denote that the path argument refers to an Amazon S3 folder.sq���Backup version to restore from. If not specified the latest backup in the specified location will be used.sE���The name of the cluster. The default is "Development Cluster".sy���The location in Amazon S3 to write the log files of the cluster. If a value is not provided, logs are not created.sq���Allows EMR to call other AWS Services such as EC2 on your behalf.To create the default Service Role <code>s����</code>, use <code>aws emr create-default-roles</code> command. This command will also create the default EC2 instance profile <code>s���</code>.sW���Allows EMR to call other service such as AnyScale and CloudWatch on your behalf.s���Uses --service-role=<code>s4���</code>, and --ec2-attributes InstanceProfile=<code>sz���</code>To create the default service role and instance profile use <code>aws emr create-default-roles</code> command. s��The version number of the Amazon Machine Image (AMI) to use for Amazon EC2 instances in the cluster. For example,--ami-version 3.1.0 You cannot specify both a release label (emr-4.0.0 and later) and an AMI version (3.x or 2.x) on a clusterFor details about the AMIs currently supported by Amazon Elastic MapReduce, go to AMI Versions Supported in Amazon Elastic MapReduce in the Amazon Elastic MapReduce Developer's Guide.http://docs.aws.amazon.com/ElasticMapReduce/latest/DeveloperGuide/ami-versions-supported.htmls���The identifier for the EMR release, which includes a set of software, to use with Amazon EC2 instances that are part of an Amazon EMR cluster. For example, --release-label emr-4.0.0 You cannot specify both a release label (emr-4.0.0 and later) and AMI version (3.x or 2.x) on a cluster.For details about the releases available in Amazon Elastic MapReduce, go to Releases Available in Amazon Elastic MapReduce in the Amazon Elastic MapReduce Documentation.http://docs.aws.amazon.com/ElasticMapReduce/latest/Applications/emr-release.htmlPlease use ami-version if you want to specify AMI Versions for your Amazon EMR cluster (3.x and 2.x)s���Specifies new configuration values for applications installed on your cluster when using an EMR release (emr-4.0.0 and later). The configuration files available for editing in each application (for example: yarn-site for YARN) can be found in the Amazon EMR Developer's Guide in the respective application's section. Currently on the CLI, you can only specify these values in a JSON file stored locally or in Amazon S3, and you supply the path to this file to this parameter. For example:<li>To specify configurations from a local file <code>--configurations file://configurations.json</code></li> <li>To specify configurations from a file in Amazon S3 <code>--configurations https://s3.amazonaws.com/myBucket/configurations.json</code></li>For more information about configuring applications in EMR release, go to the Amazon EMR Documentation: http://docs.aws.amazon.com/ElasticMapReduce/latest/Applications/emr-configure-apps.htmlsU��A specification of the number and type of Amazon EC2 instances to create instance groups in a cluster. Each instance group takes the following parameters: <code>[Name], InstanceGroupType, InstanceType, InstanceCount, [BidPrice], [EbsConfiguration], [AutoScalingPolicy]</code>. [EbsConfiguration] and [AutoScalingPolicy] are optional. EbsConfiguration takes the following parameters: <code>EbsOptimized</code> and <code>EbsBlockDeviceConfigs</code>. EbsBlockDeviceConfigs is an array of EBS volume specifications, which takes the following parameters : <code>([VolumeType], [SizeInGB], Iops)</code> and VolumesPerInstance which is the count of EBS volumes per instance with this specification. AutoScalingPolicy takes the following parameters: <code>Constraints</code> and <code>Rules</code>. Constraints takes the following parameters: <code>MinCapacity, MaxCapacity</code>. Rules is a list of AutoScaling rules associated to the policy. Each rule has the following parameters: <code> Name, [Description], Action, Trigger</code>. Action takes the following parameters: <code>Market, SimpleScalingPolicyConfiguration (AdjustmentType, ScalingAdjustment)</code>. Trigger takes <code>CloudWatchAlarmDefinition(AlarmNamePrefix, ComparisonOperator, EvaluationPeriods, MetricName, Namespace, Period, Statistic, Threshold, Unit, [Dimensions])</code>.s��� A specification of the number and type of Amazon EC2 instances used to create instance fleets in a cluster. Each instance fleet takes the following parameters: <code>[Name], InstanceFleetType, InstanceTypeConfigs, TargetOnDemandCapacity or TargetSpotCapacity, [BidPrice], [EbsConfiguration]</code>. [EbsConfiguration] is optional. EbsConfiguration takes the following parameters: <code>EbsOptimized</code> and <code>EbsBlockDeviceConfigs</code>. EbsBlockDeviceConfigs is an array of EBS volume specifications, which takes the following parameters : <code>([VolumeType], [SizeInGB], Iops)</code> and VolumesPerInstance. VolumesPerInstance is the count of EBS volumes per instance with this specification.s)��Shortcut option for --instance-groups. A specification of the type of Amazon EC2 instances used together with --instance-count (optional) to create instance groups in a cluster. Specifying the --instance-type argument without also specifying --instance-count launches a single-node cluster.s���Shortcut option for --instance-groups. A specification of the number of Amazon EC2 instances used together with --instance-type to create instance groups in a cluster. EMR will use one node as the cluster's master node and use the remainder of the nodes as core nodes. Specifying the --instance-type argument without also specifying --instance-count launches a single-node cluster.s?���Specifies additional information during cluster creationsN��Specifies the following Amazon EC2 attributes: KeyName, AvailabilityZone, SubnetId, InstanceProfile, EmrManagedMasterSecurityGroup, EmrManagedSlaveSecurityGroup, AdditionalMasterSecurityGroups and AdditionalSlaveSecurityGroups. AvailabilityZone and Subnet cannot be specified together. To create the default instance profile <code>s����</code>, use <code>aws emr create-default-roles</code> command. This command will also create the default EMR service role <code>s���</code>.<li>KeyName - the name of the AWS EC2 key pair you are using to launch the cluster.</li><li>AvailabilityZone - An isolated resource location within a region.</li><li>SubnetId - Assign the EMR cluster to this Amazon VPC Subnet. </li><li>InstanceProfile - Provides access to other AWS services such as S3, DynamoDB from EC2 instances that are launched by EMR.. </li><li>EmrManagedMasterSecurityGroup - The identifier of the Amazon EC2 security group for the master node. </li><li>EmrManagedSlaveSecurityGroup - The identifier of the Amazon EC2 security group for the slave nodes.</li><li>ServiceAccessSecurityGroup - The identifier of the Amazon EC2 security group for the Amazon EMR service to access clusters in VPC private subnets </li><li>AdditionalMasterSecurityGroups - A list of additional Amazon EC2 security group IDs for the master node</li><li>AdditionalSlaveSecurityGroups - A list of additional Amazon EC2 security group IDs for the slave nodes.</li>sy���Specifies whether the cluster should terminate after completing all the steps. Auto termination is off by default.s����Specifies whether to lock the cluster to prevent the Amazon EC2 instances from being terminated by API call, user intervention, or in the event of an error. Termination protection is off by default.s����Specifies the Scale down behavior for the cluster.The valid values are:<li>TERMINATE_AT_TASK_COMPLETION</li><li>TERMINATE_AT_INSTANCE_HOUR</li>s���Specifies whether the cluster is visible to all IAM users of the AWS account associated with the cluster. If set to <code>--visible-to-all-users</code>, all IAM users of that AWS account can view and (if they have the proper policy permisions set) manage the cluster. If it is set to <code>--no-visible-to-all-users</code>, only the IAM user that created the cluster can view and manage it. Clusters are visible by default. s��Enables debugging for the cluster. The debugging tool is a graphical user interface that you can use to browse the log files from the console (<link>https://console.aws.amazon.com/elasticmapreduce/</link> ). When you enable debugging on a cluster, Amazon EMR archives the log files to Amazon S3 and then indexes those files. You can then use the graphical interface to browse the step, job, task, and task attempt logs for the cluster in an intuitive way.Requires <code>--log-uri</code> to be specifieds���A list of tags to associate with a cluster and propagate to each Amazon EC2 instance in the cluster. They are user-defined key/value pairs that consist of a required key string with a maximum of 128 characters and an optional value string with a maximum of 256 characters.You can specify tags in <code>key=value</code> format or to add a tag without value just write key name, <code>key</code>.Syntax:Multiple tags separated by a space. --tags key1=value1 key2=value2s���Specifies a list of bootstrap actions to run when creating a cluster. You can use bootstrap actions to install additional software and to change the configuration of applications on the cluster. Bootstrap actions are scripts that are run on the cluster nodes when Amazon EMR launches the cluster. They run before Hadoop starts and before the node begins processing data.Each bootstrap action takes the following parameters: <code>Path</code>, <code>[Name]</code> and <code>[Args]</code>. Note: Args should either be a comma-separated list of values (e.g. Args=arg1,arg2,arg3) or a bracket-enclosed list of values and/or key-value pairs (e.g. Args=[arg1,arg2=arg3,arg4]).s`��Installs applications such as Hadoop, Spark, Hue, Hive, Pig, HBase, Ganglia and Impala or the MapR distribution when creating a cluster. Available applications vary by EMR release, and the set of components installed when specifying an Application Name can be found in the Amazon EMR Developer's Guide. Note: If you are using an AMI version instead of an EMR release, some applications take optional Args for configuration. Args should either be a comma-separated list of values (e.g. Args=arg1,arg2,arg3) or a bracket-enclosed list of values and/or key-value pairs (e.g. Args=[arg1,arg2=arg3,arg4]).sv��Configures certain features in EMRFS like consistent view, Amazon S3 client-side and server-side encryption.<li>Encryption - enables Amazon S3 server-side encryption or Amazon S3 client-side encryption and takes the mutually exclusive values, ServerSide or ClientSide.</li><li>ProviderType - the encryption ProviderType, which is either Custom or KMS</li> <li>KMSKeyId - the AWS KMS KeyId, the alias you mapped to the KeyId, or the full ARN of the key that includes the region, account ID, and the KeyId.</li><li>CustomProviderLocation - the S3 URI of the custom EncryptionMaterialsProvider class.</li><li>CustomProviderClass - the name of the custom EncryptionMaterialsProvider class you are using.</li><li>Consistent - setting to true enables consistent view.</li><li>RetryCount - the number of times EMRFS consistent view will check for list consistency before returning an error.</li><li>RetryPeriod - the interval at which EMRFS consistent view will recheck for consistency of objects it tracks.</li><li>SSE - deprecated in favor of Encryption=ServerSide</li><li>Args - optional arguments you can supply in configuring EMRFS.</li>s����Launches a new HBase cluster and populates it with data from a previous backup of an HBase cluster. You must install HBase using the <code>--applications</code> option. Note: this is only supported by AMI versions (3.x and 2.x).s\��A list of steps to be executed by the cluster. A step can be specified either using the shorthand syntax, JSON file or as a JSON string. Note: [Args] supplied with steps should either be a comma-separated list of values (e.g. Args=arg1,arg2,arg3) or a bracket-enclosed list of values and/or key-value pairs (e.g. Args=[arg1,arg2=arg3,arg4]).sm���The applications to be installed. Takes the following parameters: <code>Name</code> and <code>Args</code>.s��The cluster state filters to apply when listing clusters.Syntax:"string" "string" ...Where valid values are:<li>STARTING</li><li>BOOTSTRAPPING</li><li>RUNNING</li><li>WAITING</li><li>TERMINATING</li><li>TERMINATED</li><li>TERMINATED_WITH_ERRORS</li>s ��Shortcut option for --cluster-states. <li>--active filters clusters in 'STARTING','BOOTSTRAPPING','RUNNING','WAITING', or 'TERMINATING' states. </li><li>--terminated filters clusters in 'TERMINATED' state. </li><li>--failed filters clusters in 'TERMINATED_WITH_ERRORS' state. </li>sq���The creation date and time beginning value filter for listing clusters. For example, 2014-07-15T00:01:30. sk���The creation date and time end value filter for listing clusters. For example, 2014-07-15T00:01:30. sK���The identifier of the Amazon EC2 security group for the master node.sK���The identifier of the Amazon EC2 security group for the slave nodes.s|���The identifier of the Amazon EC2 security group for the Amazon EMR service to access clusters in VPC private subnets.sN��� A list of additional Amazon EC2 security group IDs for the master nodesN���A list of additional Amazon EC2 security group IDs for the slave nodes.s>���This command is only available for AMI Versions (3.x and 2.x).s���Creates an Amazon EMR cluster with specified software.

Quick start:

aws emr create-cluster --release-label <release-label> --instance-type <instance-type> [--instance-count <instance-count>]

Values for variables Instance Profile (under EC2 Attributes), Service Role, Log URI, and Key Name (under EC2 Attributes) can be set in the AWS CLI config file using the "aws configure set" command.
s����The name of a security configuration in the AWS account. Use <code>list-security-configurations</code> to get a list of available security configurations.N(-���t,���awscli.customizations.emr.createdefaultrolesR����R���t���TERMINATE_CLUSTERSt
���CLUSTER_IDt���HBASE_BACKUP_DIRt���HBASE_BACKUP_VERSIONt���CLUSTER_NAMEt���LOG_URIt���SERVICE_ROLEt���AUTOSCALING_ROLEt���USE_DEFAULT_ROLESt���AMI_VERSIONt
���RELEASE_LABELt���CONFIGURATIONSt���INSTANCE_GROUPSt���INSTANCE_FLEETSt
���INSTANCE_TYPEt���INSTANCE_COUNTt���ADDITIONAL_INFOt���EC2_ATTRIBUTESt���AUTO_TERMINATEt���TERMINATION_PROTECTEDt���SCALE_DOWN_BEHAVIORt
���VISIBILITYt	���DEBUGGINGt���TAGSt���BOOTSTRAP_ACTIONSt���APPLICATIONSt���EMR_FSt���RESTORE_FROM_HBASEt���STEPSt���INSTALL_APPLICATIONSt���LIST_CLUSTERS_CLUSTER_STATESt���LIST_CLUSTERS_STATE_FILTERSt���LIST_CLUSTERS_CREATED_AFTERt���LIST_CLUSTERS_CREATED_BEFOREt!���EMR_MANAGED_MASTER_SECURITY_GROUPt ���EMR_MANAGED_SLAVE_SECURITY_GROUPt���SERVICE_ACCESS_SECURITY_GROUPt!���ADDITIONAL_MASTER_SECURITY_GROUPSt ���ADDITIONAL_SLAVE_SECURITY_GROUPSt���AVAILABLE_ONLY_FOR_AMI_VERSIONSt���CREATE_CLUSTER_DESCRIPTIONt���SECURITY_CONFIG(����(����(����sB���/tmp/pip-build-uEGWVr/awscli/awscli/customizations/emr/helptext.pyt���<module>���sV���

Name	Size	Permission
__init__.py	565 bytes	0644
__init__.pyc	153 bytes	0644
addinstancegroups.py	2505 bytes	0644
addinstancegroups.pyc	2145 bytes	0644
addsteps.py	1947 bytes	0644
addsteps.pyc	1673 bytes	0644
addtags.py	1089 bytes	0644
addtags.pyc	1149 bytes	0644
applicationutils.py	6550 bytes	0644
applicationutils.pyc	5456 bytes	0644
argumentschema.py	29545 bytes	0644
argumentschema.pyc	12185 bytes	0644
command.py	5442 bytes	0644
command.pyc	4233 bytes	0644
config.py	4761 bytes	0644
config.pyc	5735 bytes	0644
configutils.py	2554 bytes	0644
configutils.pyc	3195 bytes	0644
constants.py	6625 bytes	0644
constants.pyc	7405 bytes	0644
createcluster.py	23006 bytes	0644
createcluster.pyc	15561 bytes	0644
createdefaultroles.py	13460 bytes	0644
createdefaultroles.pyc	10750 bytes	0644
describecluster.py	4728 bytes	0644
describecluster.pyc	3442 bytes	0644
emr.py	3257 bytes	0644
emr.pyc	3057 bytes	0644
emrfsutils.py	9106 bytes	0644
emrfsutils.pyc	8048 bytes	0644
emrutils.py	8301 bytes	0644
emrutils.pyc	9588 bytes	0644
exceptions.py	10086 bytes	0644
exceptions.pyc	14784 bytes	0644
hbase.py	9454 bytes	0644
hbase.pyc	8039 bytes	0644
hbaseutils.py	953 bytes	0644
hbaseutils.pyc	666 bytes	0644
helptext.py	18959 bytes	0644
helptext.pyc	17018 bytes	0644
installapplications.py	2879 bytes	0644
installapplications.pyc	2467 bytes	0644
instancefleetsutils.py	2479 bytes	0644
instancefleetsutils.pyc	1367 bytes	0644
instancegroupsutils.py	3378 bytes	0644
instancegroupsutils.pyc	2283 bytes	0644
listclusters.py	3775 bytes	0644
listclusters.pyc	4361 bytes	0644
modifyclusterattributes.py	3639 bytes	0644
modifyclusterattributes.pyc	2511 bytes	0644
ssh.py	7731 bytes	0644
ssh.pyc	6362 bytes	0644
sshutils.py	3354 bytes	0644
sshutils.pyc	3527 bytes	0644
steputils.py	8482 bytes	0644
steputils.pyc	6895 bytes	0644
terminateclusters.py	1382 bytes	0644
terminateclusters.pyc	1332 bytes	0644