- Le plus récent
- Le plus de votes
- La plupart des commentaires
It seems the problem was that this does not work :
aws ssm start-session --profile <my_profile> --target <instance_id>
but this does :
aws ssm start-session --target <instance_id>
It seems that the issue is related to the connectivity of the GameLift Fleet instance. Here are a few things that you can check:
- Make sure that the instance is in a running state and is able to communicate with the AWS SSM service. You can check the instance status in the GameLift console or by running the following command:
aws gamelift --profile <my_profile> describe-instances --fleet-id <fleet_id> --instance-ids <instance_id>
- Verify that the instance has the AWS SSM agent installed and running. You can check the agent status by connecting to the instance using SSH and running the following command:
sudo systemctl status amazon-ssm-agent
If the agent is not running, you can start it using the following command:
sudo systemctl start amazon-ssm-agent
- Check if the instance is configured to allow SSM sessions. You can verify this by checking the instance profile associated with the instance. Make sure that the instance profile has the required permissions to start an SSM session. You can check the instance profile by running the following command:
aws gamelift --profile <my_profile> describe-instance-attributes --fleet-id <fleet_id> --attribute-names instanceAccess
The output should show the instance profile name and the SSM role ARN associated with the instance.
If you still encounter issues, you may want to check the GameLift and SSM logs for any errors or warnings that could indicate the source of the problem.
Thank you for your answer. How may I SSH into the instance to check the SSM agent ? It seems I cannot. When I try the old way (get-instance-access) I get this error :
An error occurred (InvalidRequestException) when calling the GetInstanceAccess operation: This API does not support fleets using builds integrated with GameLift Server SDK 5 and above. Use the GetComputeAccess operation to access this fleet resource.
The command
describe-instance-attributes
does not seem to exist, I can only finddescribe-fleet-attributes
Contenus pertinents
- Réponse acceptéedemandé il y a un an
- demandé il y a 5 mois
- demandé il y a un an
- demandé il y a 14 jours
- AWS OFFICIELA mis à jour il y a 5 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 5 ans
For future reference to those confused. This behavior is due to the credential profile option overriding exported access credentials provided by the get-compute-access call (see link below). Since the compute for a Managed EC2 fleet is not owned by one's personal AWS account, SSM will fail to find the instance id.
AWS CLI precedence: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-authentication.html#cli-chap-authentication-precedence