- Newest
- Most votes
- Most comments
Thanks for the reply. I'll try to sign into the fleet directly and see if I can discover anything there. I'm fairly confident we aren't running into issues w/ hardcoded paths, I'll make another pass and verify we aren't missing an library files.
This was the message that we received when trying to upload our build:
Fleet creation error: InvalidRequestException: The c6a.xlarge instance type is only supported on SDK 5 and above fleets.
It had been working for a while before we hit this around July 14th.
Hey Jesse,
we recently ran into an issue where our desired instance type was no longer available unless we upgraded to SDK 5 (started getting build upload failures saying such.)
Could you elaborate on what the error was, what instance type you wanted, and where you encountered the error (API call, fleet event, etc.), so the team can investigate further? Thank you!
Since your build is working in Anywhere but failing in Managed EC2, I would recommend verifying you don't have hard-coded filepaths that could break when deployed to a different system, and that you are bundling all dependencies (.dll or .so) your game server relies on into your zip file.
Additionally, you can directly sign-in to your fleet's compute by following this re:Post answer: https://repost.aws/questions/QUKtsf6-brR4yhhYTL1Taniw/connect-to-windows-server-2016-gamelift-instance-with-sdk-version-5#ANhWlxD6VdQEaEEROOLc1UMg . That way you can run the application yourself and see all logs to help debug your server and your connections to Sentry.
Lastly, this is a useful guide in our documentation for migrating to SDK version 5: https://docs.aws.amazon.com/gamelift/latest/developerguide/reference-serversdk.html#fleet-anywhere-sdk
Regards,
Relevant content
- asked 4 months ago
- asked 3 years ago
AWS OFFICIALUpdated 7 months ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
Hey Jesse, would you mind trying to create an SDK 4 fleet with that instance type again? I reached out to the team and they indicated this was unintentional and should be back to normal now.
If you're still hitting that InvalidRequestException, could you let me know what AWS Region you're calling into? Thanks!
Oh that's good to know, will do. Thanks!
The c6a.xlarge instance type is indeed working again. While this doesn't solve the issue I asked about, it does solve the underlying issue I'm trying to solve. I won't mark the chain accepted (I don't want to give future readers false hope if they have the same problem.) But I don't need anymore assistance. Thanks.