Hadoop - ne peux pas ssh dans Elastic MapReduce - Stack Overflow

I'm using elastic-mapreduce to spun new clusters from the command line. After reading this tutorial, I have:

elastic-mapreduce --create --alive \
--instance-type m1.xlarge\
--num-instances 5 \
--supported-product mapr \
--name m7 \
--args "--edition,m7"

a new cluster with 6 nodes(1 master + 5 slaves) will be created. So I try to ssh into the master:

elastic-mapreduce --jobflow j-3FLVMX9CYE5L6 --ssh

and I get Permission denied (publickey) The permissions.json file is in the elastic_mapreduce home, and also the path to the my_key.pem file. Also, by doing:

ssh -i my_key.pem hadoop@masternode

I also get Permission denied (publickey). my_key.pem has been given 400 permissions. I honestly don't know what can I try next ... any clues?

When I go to the EC2 console, and I click in Connect, I get the following error message:

Instance is not associated with a key pair.
This instance is not associated with a Key Pair. Without a Key Pair you will need to log into this instance using a valid username and password combination.

When you create your EMR cluster make sure you enable a key pair. On EMR console you can see it like below:

I'm using elastic-mapreduce to spun new clusters from the command line. After reading this tutorial, I have:

elastic-mapreduce --create --alive \
--instance-type m1.xlarge\
--num-instances 5 \
--supported-product mapr \
--name m7 \
--args "--edition,m7"

a new cluster with 6 nodes(1 master + 5 slaves) will be created. So I try to ssh into the master:

elastic-mapreduce --jobflow j-3FLVMX9CYE5L6 --ssh

and I get Permission denied (publickey) The permissions.json file is in the elastic_mapreduce home, and also the path to the my_key.pem file. Also, by doing:

ssh -i my_key.pem hadoop@masternode

I also get Permission denied (publickey). my_key.pem has been given 400 permissions. I honestly don't know what can I try next ... any clues?

When I go to the EC2 console, and I click in Connect, I get the following error message:

Instance is not associated with a key pair.
This instance is not associated with a Key Pair. Without a Key Pair you will need to log into this instance using a valid username and password combination.

When you create your EMR cluster make sure you enable a key pair. On EMR console you can see it like below:

Source