

Le traduzioni sono generate tramite traduzione automatica. In caso di conflitto tra il contenuto di una traduzione e la versione originale in Inglese, quest'ultima prevarrà.

# Utilizzo di AWS SDK per Java per creare un cluster Amazon EMR
<a name="calling-emr-with-java-sdk"></a>

 AWS SDK per Java Fornisce tre pacchetti con funzionalità Amazon EMR:
+  [com.amazonaws.services.elasticmapreduce](https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/elasticmapreduce/package-summary.html) 
+  [com.amazonaws.services.elasticmapreduce.model](https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/elasticmapreduce/model/package-summary.html) 
+  [com.amazonaws.services.elasticmapreduce.util](https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/elasticmapreduce/util/package-summary.html) 

Per ulteriori informazioni su questi pacchetti, consulta la [Guida di riferimento alle API di AWS SDK per Java](https://docs.aws.amazon.com/sdk-for-java/latest/reference/).

L'esempio seguente illustra come SDKs possono semplificare la programmazione con Amazon EMR. Il codice di esempio sottostante utilizza l'oggetto `StepFactory`, una classe helper per la creazione di tipi di fase Amazon EMR comuni, per creare un cluster Hive interattivo con il debug abilitato. 

```
import com.amazonaws.AmazonClientException;
import com.amazonaws.auth.AWSCredentials;
import com.amazonaws.auth.AWSStaticCredentialsProvider;
import com.amazonaws.auth.profile.ProfileCredentialsProvider;
import com.amazonaws.services.elasticmapreduce.AmazonElasticMapReduce;
import com.amazonaws.services.elasticmapreduce.AmazonElasticMapReduceClientBuilder;
import com.amazonaws.services.elasticmapreduce.model.*;
import com.amazonaws.services.elasticmapreduce.util.StepFactory;

public class Main {

	public static void main(String[] args) {
		AWSCredentialsProvider profile = null;
		try {
			credentials_profile = new ProfileCredentialsProvider("default"); // specifies any named profile in
																																				// .aws/credentials as the credentials provider
		} catch (Exception e) {
			throw new AmazonClientException(
					"Cannot load credentials from .aws/credentials file. " +
							"Make sure that the credentials file exists and that the profile name is defined within it.",
					e);
		}

		// create an EMR client using the credentials and region specified in order to
		// create the cluster
		AmazonElasticMapReduce emr = AmazonElasticMapReduceClientBuilder.standard()
				.withCredentials(credentials_profile)
				.withRegion(Regions.US_WEST_1)
				.build();

		// create a step to enable debugging in the AWS Management Console
		StepFactory stepFactory = new StepFactory();
		StepConfig enabledebugging = new StepConfig()
				.withName("Enable debugging")
				.withActionOnFailure("TERMINATE_JOB_FLOW")
				.withHadoopJarStep(stepFactory.newEnableDebuggingStep());

		// specify applications to be installed and configured when EMR creates the
		// cluster
		Application hive = new Application().withName("Hive");
		Application spark = new Application().withName("Spark");
		Application ganglia = new Application().withName("Ganglia");
		Application zeppelin = new Application().withName("Zeppelin");

		// create the cluster
		RunJobFlowRequest request = new RunJobFlowRequest()
				.withName("MyClusterCreatedFromJava")
				.withReleaseLabel("emr-5.20.0") // specifies the EMR release version label, we recommend the latest release
				.withSteps(enabledebugging)
				.withApplications(hive, spark, ganglia, zeppelin)
				.withLogUri("s3://path/to/my/emr/logs") // a URI in S3 for log files is required when debugging is enabled
				.withServiceRole("EMR_DefaultRole") // replace the default with a custom IAM service role if one is used
				.withJobFlowRole("EMR_EC2_DefaultRole") // replace the default with a custom EMR role for the EC2 instance
																								// profile if one is used
				.withInstances(new JobFlowInstancesConfig()
						.withEc2SubnetId("subnet-12ab34c56")
						.withEc2KeyName("myEc2Key")
						.withInstanceCount(3)
						.withKeepJobFlowAliveWhenNoSteps(true)
						.withMasterInstanceType("m4.large")
						.withSlaveInstanceType("m4.large"));

		RunJobFlowResult result = emr.runJobFlow(request);
		System.out.println("The cluster ID is " + result.toString());

	}

}
```

Come minimo, è necessario assegnare un ruolo di servizio e un ruolo jobflow corrispondenti rispettivamente a EMR\_ DefaultRole e EMR\_ \_. EC2 DefaultRole È possibile farlo richiamando questo comando per lo stesso account. AWS CLI Innanzitutto, verifica se i ruoli esistono già: 

```
aws iam list-roles | grep EMR
```

Se esistono, verranno visualizzati sia il profilo dell'istanza (EC2EMR\_ \_DefaultRole) che il ruolo di servizio (EMR\_DefaultRole): 

```
"RoleName": "EMR_DefaultRole", 
            "Arn": "arn:aws:iam::{{AccountID}}:role/EMR_DefaultRole"
            "RoleName": "EMR_EC2_DefaultRole", 
            "Arn": "arn:aws:iam::{{AccountID}}:role/EMR_EC2_DefaultRole"
```

Se i ruoli predefiniti non esistono, puoi utilizzare il seguente comando per crearli:

```
aws emr create-default-roles
```