cannot ssh to my new instance of EC2/AWS
I am new to AWS up in front. I launched an Ubuntu instance in EC2. I created keypair. Initially I opened TCP/80, TCP/22 from all IP's. For debugging I opened all the ports in the fire wall.
When I execute on my desktop machine:
ssh -i "awskeypair3.pem" ubuntu@ec2-xxxxxxxx.us-east-2.compute.amazonaws.com
I get timeout.
ping ec2-xxxxxxxx.us-east-2.compute.amazonaws.com
I get timeout.
I am really not sure what I am doing. So feel free to start at the bottom floor.
I am medium familiar with Ubuntu and ssh. But not with AWS.
ubuntu ssh amazon-web-services amazon-ec2
add a comment |
I am new to AWS up in front. I launched an Ubuntu instance in EC2. I created keypair. Initially I opened TCP/80, TCP/22 from all IP's. For debugging I opened all the ports in the fire wall.
When I execute on my desktop machine:
ssh -i "awskeypair3.pem" ubuntu@ec2-xxxxxxxx.us-east-2.compute.amazonaws.com
I get timeout.
ping ec2-xxxxxxxx.us-east-2.compute.amazonaws.com
I get timeout.
I am really not sure what I am doing. So feel free to start at the bottom floor.
I am medium familiar with Ubuntu and ssh. But not with AWS.
ubuntu ssh amazon-web-services amazon-ec2
add a comment |
I am new to AWS up in front. I launched an Ubuntu instance in EC2. I created keypair. Initially I opened TCP/80, TCP/22 from all IP's. For debugging I opened all the ports in the fire wall.
When I execute on my desktop machine:
ssh -i "awskeypair3.pem" ubuntu@ec2-xxxxxxxx.us-east-2.compute.amazonaws.com
I get timeout.
ping ec2-xxxxxxxx.us-east-2.compute.amazonaws.com
I get timeout.
I am really not sure what I am doing. So feel free to start at the bottom floor.
I am medium familiar with Ubuntu and ssh. But not with AWS.
ubuntu ssh amazon-web-services amazon-ec2
I am new to AWS up in front. I launched an Ubuntu instance in EC2. I created keypair. Initially I opened TCP/80, TCP/22 from all IP's. For debugging I opened all the ports in the fire wall.
When I execute on my desktop machine:
ssh -i "awskeypair3.pem" ubuntu@ec2-xxxxxxxx.us-east-2.compute.amazonaws.com
I get timeout.
ping ec2-xxxxxxxx.us-east-2.compute.amazonaws.com
I get timeout.
I am really not sure what I am doing. So feel free to start at the bottom floor.
I am medium familiar with Ubuntu and ssh. But not with AWS.
ubuntu ssh amazon-web-services amazon-ec2
ubuntu ssh amazon-web-services amazon-ec2
edited Feb 10 at 20:19
Tim
37827
37827
asked Feb 10 at 7:36
user2712329user2712329
1
1
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Try check few things:
ec2 machine host name / ip. The ip and hostname change if you stopped / started your ec2 instance. This could be misleading at first
security group is authorizing inbound connections from all ip on port 22
This in general should do the job. Not sure that icmp ping requests are enabled by default on ec2 instances. You may have to configure that in the security group too.
You can use tcping or telnet to make sure the port is open.
add a comment |
Did you lower the permissions of the pem file with chmod? Check if you're in the same directory as your key when using the above syntax.
Also, to be able to ping you also need to open ICMP protocol in security groups.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404068%2fcannot-ssh-to-my-new-instance-of-ec2-aws%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try check few things:
ec2 machine host name / ip. The ip and hostname change if you stopped / started your ec2 instance. This could be misleading at first
security group is authorizing inbound connections from all ip on port 22
This in general should do the job. Not sure that icmp ping requests are enabled by default on ec2 instances. You may have to configure that in the security group too.
You can use tcping or telnet to make sure the port is open.
add a comment |
Try check few things:
ec2 machine host name / ip. The ip and hostname change if you stopped / started your ec2 instance. This could be misleading at first
security group is authorizing inbound connections from all ip on port 22
This in general should do the job. Not sure that icmp ping requests are enabled by default on ec2 instances. You may have to configure that in the security group too.
You can use tcping or telnet to make sure the port is open.
add a comment |
Try check few things:
ec2 machine host name / ip. The ip and hostname change if you stopped / started your ec2 instance. This could be misleading at first
security group is authorizing inbound connections from all ip on port 22
This in general should do the job. Not sure that icmp ping requests are enabled by default on ec2 instances. You may have to configure that in the security group too.
You can use tcping or telnet to make sure the port is open.
Try check few things:
ec2 machine host name / ip. The ip and hostname change if you stopped / started your ec2 instance. This could be misleading at first
security group is authorizing inbound connections from all ip on port 22
This in general should do the job. Not sure that icmp ping requests are enabled by default on ec2 instances. You may have to configure that in the security group too.
You can use tcping or telnet to make sure the port is open.
answered Feb 10 at 10:15
Hichem BOUSSETTAHichem BOUSSETTA
1012
1012
add a comment |
add a comment |
Did you lower the permissions of the pem file with chmod? Check if you're in the same directory as your key when using the above syntax.
Also, to be able to ping you also need to open ICMP protocol in security groups.
add a comment |
Did you lower the permissions of the pem file with chmod? Check if you're in the same directory as your key when using the above syntax.
Also, to be able to ping you also need to open ICMP protocol in security groups.
add a comment |
Did you lower the permissions of the pem file with chmod? Check if you're in the same directory as your key when using the above syntax.
Also, to be able to ping you also need to open ICMP protocol in security groups.
Did you lower the permissions of the pem file with chmod? Check if you're in the same directory as your key when using the above syntax.
Also, to be able to ping you also need to open ICMP protocol in security groups.
answered Feb 10 at 10:34
AnushikAnushik
63
63
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404068%2fcannot-ssh-to-my-new-instance-of-ec2-aws%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown