Struggling to connect to EC2 instance via Fleet Manager

Question

I've been using Fleet Manager for my instances for a while now, all the instances that have worked have been of the same AMI, same instance type, same key-pair and same security group. However, this time around I decided to change the AMI and instance type to the following:

AMI: vgpu16.3-nv-windows-server-2022-vWS-538.15-v202401160712-prod-77u2eeb33lmrm Instance Type: g4dn.4xlarge

And now it doesn't work. Any advice on this? :)

AMI: vgpu16.3-nv-windows-server-2022-vWS-538.15-v202401160712-prod-77u2eeb33lmrm
Instance Type: g4dn.4xlarge

And now it doesn't work. Any advice on this? :)

Giovanni Lauria · Answer

Check that the AMI you specified is supported by Fleet Manager for that instance type. Not all AMIs work on all instance types.

Verify that the IAM role used by the fleet has the necessary permissions for the new instance type. Some instance types require additional permissions.

Make sure the security group allows access to the new instance type. Some instance types may use different ports.

Stop the existing fleet before editing the fleet configuration with the new AMI and instance type. Then start the fleet again.

Review AWS documentation for the latest instance type specifications and AMI guidelines for Fleet Manager. The combination of AMI and instance type may not be supported.

As a test, try launching a single EC2 instance with the new AMI and instance type using the AWS console to see if it comes up successfully. This will validate the AMI and instance type are configured correctly before using with Fleet Manager.

Let me know if stopping the fleet, updating the configuration, and restarting doesn't resolve the issue.

Struggling to connect to EC2 instance via Fleet Manager

Relevant content