<commit_before>##Accounts

###Cloudbreak account

First and foremost in order to start launching Hadoop clusters you will need to create a Cloudbreak account. C
loudbreak supports registration, forgotten and reset password, and login features at API level.
All password are stored or sent are hashed - communication is always over a secure HTTPS channel. When you are deploying your own Cloudbreak instance we strongy suggest to configure an SSL certificate.
Users create and launch Hadoop clusters on their own namespace and security context. 

Cloudbreak is launching Hadoop clusters on the user's behalf - on different cloud providers. One key point is that Cloudbreak **does not** store your Cloud provider account details (such as username, passord, keys, private SSL certificates, etc).
We work around the concept that Identity and Access Management is fully controlled by you - the end user. The Cloudbreak *deployer* is purelly acting on behalf of the end user - without having access to the user's account. 

**How does this work**?

###Configuring the AWS EC2 account

Once you have logged in Cloudbreak you will have to link your AWS account with the Cloudbreak one. In order to do that you will need to do configure two IAM Roes

1. Log in AWS management console with the user account you'd like to use with Cloudbreak
2. Go to IAM and select Roles
  * Select Role for Cross-Account access 
    *  Allows IAM users from a 3rd party AWS account to access this account.
    
      **Account ID:** In case you are using our hosted solution you will need to pass SequenceIQ's account id: 755047402263

      **External ID:** provision-ambari (association link)
      
    * Custom policy 
      Use this policy [document](https://raw.githubusercontent.com/sequenceiq/cloudbreak/documentation/src/main/resources/iam-arn-custom.policy?token=<KEY>) to configure the permission to start EC2 instances on the end user's behalf, and use SNS to receive notifications.
      
  * Select AWS Service Role
    * Amazon EC2
    *  Select Policy template - Read Only Access 
   

Once these are configured, Cloudbreak is ready to launch Hadoop clusters on your behalf. The only thing Cloudbreak requires are the `Role ARN` (Role for Cross-Account access) and the `Instance Profile ARN(s)` (AWS Service Roles).

<commit_msg>instace profile role ARN is not needed anymore<commit_after>##Accounts

###Cloudbreak account

First and foremost in order to start launching Hadoop clusters you will need to create a Cloudbreak account. C
loudbreak supports registration, forgotten and reset password, and login features at API level.
All password are stored or sent are hashed - communication is always over a secure HTTPS channel. When you are deploying your own Cloudbreak instance we strongy suggest to configure an SSL certificate.
Users create and launch Hadoop clusters on their own namespace and security context. 

Cloudbreak is launching Hadoop clusters on the user's behalf - on different cloud providers. One key point is that Cloudbreak **does not** store your Cloud provider account details (such as username, passord, keys, private SSL certificates, etc).
We work around the concept that Identity and Access Management is fully controlled by you - the end user. The Cloudbreak *deployer* is purely acting on behalf of the end user - without having access to the user's account. 

**How does this work**?

###Configuring the AWS EC2 account

Once you have logged in Cloudbreak you will have to link your AWS account with the Cloudbreak one. In order to do that you will need to configure an IAM Role.

1. Log in to the AWS management console with the user account you'd like to use with Cloudbreak
2. Go to IAM and select Roles
  * Select Role for Cross-Account access 
    *  Allows IAM users from a 3rd party AWS account to access this account.
    
      **Account ID:** In case you are using our hosted solution you will need to pass SequenceIQ's account id: 755047402263

      **External ID:** provision-ambari (association link)
      
    * Custom policy 
      Use this policy [document](https://raw.githubusercontent.com/sequenceiq/cloudbreak/documentation/src/main/resources/iam-arn-custom.policy?token=<KEY>) to configure the permission to start EC2 instances on the end user's behalf, and use SNS to receive notifications.
         

Once this is configured, Cloudbreak is ready to launch Hadoop clusters on your behalf. The only thing Cloudbreak requires is the `Role ARN` (Role for Cross-Account access).


{'fraction_non_alphanumeric': 0.04799823047998231, 'fraction_numerical': 0.0077416500774165, 'mean_word_length': 4.092342342342342, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5853021', 'n_tokens_mistral': 1134, 'n_tokens_neox': 1067, 'n_words': 650}