1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hello, If your are trying to add SSM agent to an Anywhere fleet, even if the server is on AWS or not, please refer to this link.
Be sure to check if the role you are assigning to the server has SSM permisions like(AmazonEC2RoleforSSM) aws Managed policy.
Finally for your error it is usually disk related, please be sure to:
- Expand the EBS root volume
- Restart the instance
- Access your instance
- Check the inotify
cat /proc/sys/fs/inotify/max_user_watches
- Modify the value to the one you think fits better
echo "fs.inotify.max_user_watches=1048576" >> /etc/sysctl.conf sysctl -p
Remember you can always open a support case so you can get Official AWS support
beantwortet vor einem Jahr
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
Hello, thanks for your reply. However, as mentioned in the original post, I am not trying to add an SSM agent to an Anywhere fleet. The Anywhere fleet is working fine. I am trying to ssh into a managed EC2 Gamelift instance.
Hi Isaac, did you tried the last part of the answer I provided, Usually that error is related to the inotify usage of the instance, and again, the AWS support will help a lot when dealing with this type of errors.
Hi gasamoma, no I did not try the last part, as step 3 "Access your instance" is exactly what I can't do, as mentioned in the original post.
What I'm trying to do is connect to my instance via ssh. Note that this is an instance managed by Gamelift 5.x.