So:
"System A" is the one you call "Master", and has public IP 18.191.161.9. It
has the private IP address 172.31.20.219.
"System B" is the one you call "Client", and has the private IP address
172.31.24.31. I know this because before you changed the prompt to "Client@",
the prompt was
Please do this:
Use the AWS EC2 Console to find out the public and private addresses of the
system you want to connect FROM. We will call this system "system A".
Please post those details here.
Use the AWS EC2 Console to find out the private and public addresses of the
system you want to connect
Even now I directly tried without being an root user but it still shows the
same thing . my last logged in details. but before that it may be connect
to the client since there were no errors shown. so now I'm completely
confused and tried every combination in this week. but no idea what exactly
is
I made Changes in my sshd_config file like yes to passwordauthentication
and bunch of as shown on youtube. is that problem ? because it won't be
here it'll give permission errors then .
On Mon, Aug 13, 2018 at 7:21 PM, Kiran Sonawane <
kiransonawane.nm...@gmail.com> wrote:
> I'm Constantly
I'm Constantly getting this window. What is this ? sending a new screen shot
On Mon, Aug 13, 2018 at 7:13 PM, Kiran Sonawane <
kiransonawane.nm...@gmail.com> wrote:
> I mean i was loged out as root user and become normal use. I didn't really
> go to my remote machine. but I'm sending you screen
I mean i was loged out as root user and become normal use. I didn't really
go to my remote machine. but I'm sending you screen shots of my cmd where i
changed Insta_1.pen to 600 then try to shh -i ~/.ssh/Insta_1.pem
ubuntu@publicIP and it did the same thing as last time.
Logged out of super user
I already did that all changes, made the path on same line. Then I changed
permissions to from 777 to 666
Then I again changed to 400. Nothing worked. I just don't understand what's
happening?
All the files from /.ssh are gone. Id_rsa, Id_rsa.pub, my .pem file config
file all are not there when I
I don't think it "logged you out of superuser" - I think it logged you into
the remote system :-)
On Mon, Aug 13, 2018 at 8:25 PM, Kiran Sonawane <
kiransonawane.nm...@gmail.com> wrote:
> I just tried what you said and it just forced log out of Superuser then
> all the copied .pem file and
Hullo again.
Configuration files need to be copied exactly and accurately. Look at the
config file you sent - it does not match the formatting I sent, unless
email screwed it up. Each line - Host, Hostname, User and IdentityFile,
must be on a separate line. The value for each keyword should be on
should I mention any path for IdentityFile ?
On Mon, Aug 13, 2018 at 2:45 PM, Kiran Sonawane <
kiransonawane.nm...@gmail.com> wrote:
> i created config file in .ssh folder but now i'm getting error
>
> /root/.ssh/config line 4: Missing argument.
>
> I'm sending you config files cat screen shot
Actually I opened powershell in windows and copy the content (which was
easy) then I vi and pasted it in .ssh folder with same name and .pem
extension that's it.
On Mon, Aug 13, 2018, 2:42 PM Karl Auer wrote:
> Hullo Kiran Sonawane
>
> I'm puzzled. How did you download the .pem file onto an
i created config file in .ssh folder but now i'm getting error
/root/.ssh/config line 4: Missing argument.
I'm sending you config files cat screen shot and error screen shot
thanx in advance
On Mon, Aug 13, 2018 at 1:59 PM, Karl Auer wrote:
> I didn't notice your attachment, sorry.
>
> The
My .pem file is on remote machine (windows) how can I now copy that file
into my ec2 instance?
On Mon, Aug 13, 2018, 1:59 PM Karl Auer wrote:
> I didn't notice your attachment, sorry.
>
> The attachment indicates that you are not specifying the private key!
>
> Copy the key (that you
I didn't notice your attachment, sorry.
The attachment indicates that you are not specifying the private key!
Copy the key (that you downloaded when you created the instance) into
~/.ssh. Set it's permissions to "-rw---":
cp /path/to/downloaded/keyfile.pem ~/.ssh
chmod u=rw,go=
Hullo Kiran Sonawane
"permission denied"
is good! It means that you do have network connectivity to the instance. It
also means that either the username OR the private key (OR both :-) are
incorrect.
Turn on all the debugging you can find in putty, try connecting again, and
post the debug
now I tried connection ec2 instance from putty. then i followed all the
steps in all videos on youtube its giving the following error.
(ECDSA) to the list of known hosts.
Permission denied (publickey).
On Mon, Aug 13, 2018 at 11:46 AM, Jonathan Lozada De La Matta <
jloza...@redhat.com> wrote:
Kiran,
Your issue seems to be more an issue about connecting right to the aws vm
than ansible. Did you create the keys, downloaded them, ssh-add and
connecting as the right user? are you using -K and escalating correctly?
On Mon, Aug 13, 2018 at 2:03 AM Kiran Sonawane <
I have free account so only default instances can be created but I changed
Root Password To Root before starting so there should not be permission
issue but it gives me an permission issue.
On Sunday, August 12, 2018 at 9:39:08 PM UTC+5:30, Sakthivel G wrote:
>
> Hi,
>
> /dev/sda is reserved
I send you the file where error is permission denied. Please see if you can
help me.
On Sun, Aug 12, 2018 at 7:23 PM, Jonathan Lozada De La Matta <
jloza...@redhat.com> wrote:
> please submit an issue or a PR to update the docs if you have examples or
> figure out how it should be.
>
> On Sun,
Well, I don't know what I was looking at, but now there ARE ec2_instance
examples. I haven't checked them out beyond noting that at least they are
not ec2_instance_facts examples :-)
Maybe I was looking at older documentation.
As soon as I logged into github I found the previous bug report on
You may need to specify /dev/sda1 still, if you want to attach a larger
root volume than the AMI provides, or a volume with characteristics the
default volume does not have.
Regards, K.
On Mon, Aug 13, 2018 at 2:08 AM, Sakthivel G wrote:
> Hi,
>
> /dev/sda is reserved for root.
>
> Please try
Hi,
/dev/sda is reserved for root.
Please try below...
# Single instance with ssd gp2 root volume
- ec2:
key_name: mykey
group: webserver
instance_type: c3.medium
image: ami-123456
wait: yes
wait_timeout: 500
volumes:
- device_name: /dev/xvda
please submit an issue or a PR to update the docs if you have examples or
figure out how it should be.
On Sun, Aug 12, 2018 at 1:26 AM Karl Auer wrote:
> Yes, it's not clear. And is made worse by the fact that there are STILL no
> ec2_instance examples! The examples given are ec2_instance_facts
Yes, it's not clear. And is made worse by the fact that there are STILL no
ec2_instance examples! The examples given are ec2_instance_facts examples.
Regard, K.
On Sun, Aug 12, 2018 at 10:57 AM, Bruce Affonso
wrote:
> I am trying to use the ec2_instance module to create an ec2 instance.
>
I am trying to use the ec2_instance module to create an ec2 instance. When
using the ec2 module to configure a volume one would do something like this:
volumes:
- device_name: /dev/sda1
volume_type: gp2
volume_size: 50
With ec2_instance I am not sure how to set the values.
In the
25 matches
Mail list logo
