- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
I figured it out! The key was still correct, HOWEVER< for some reason, the username must have changed. VERY strange why it changed, but it did. So I clicked to EDIT under EXISTING COMPUTE section in my Cloud9 configuration. Then I changed the user name that was listed in lightsail to the username as well. ALSO, before it all worked, I also had to change the path as well to /home/NEW_USER_NAME.
Hi,
It looks like you ran the command using the Lightsail instance profile credentials to make the request. You have to paste in your credentials directly to have the proper permissions.
Thanks.
I am confused why there would be a credential problem since it was working a few months ago. Also, I thought if it was a credential issue it would just fail right away instead of taking 5 minutes to fail. Let me check my .ssh/authorized_keys with the AWS keys to make sure they're the same.
So, it DID work.
However, after logging in, it asked me to increase the number of "iNodes" and instructed me to run this command:
sudo bash -c 'echo "fs.inotify.max_user_watches=524288" >> /etc/sysctl.conf' && sudo sysctl -p
After running that command, I clicked to refresh the Cloud9 instance. Now it once again is showing the same original error message again about T2 or T3 instances. ALSO, I am now unable to even login via the lightsail console!
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 2 anni fa
Thank you for helping me! I was trying to simply connect from the AWS counsole. I didn't run any command on my cloud 9 because it won't let me connect to see my cloud 9 instance to even get a command prompt.
It looks like you're using the Lightsail instance profile credentials. You have to paste in your credentials directly to have the proper permissions.
Let us know if you have any other questions.