Issues updating to Server SDK 5.0.3

You can do the following if you are using Ubuntu.

1. Check if the library exist with find / -name libcrypto. so. 3 if it exist apply this export LD_LIBRARY_PATH=/path/to/lib:$LD_LIBRARY_PATH ( with the good path )
2. Install the libssl3 package sudo apt-get install libssl3-dev.
3. If that still don't work you can also simply trying reinstalling the library

And see the equivalent command in any linux flavors.

Update2: I had a script to gather logs from a fleet using get-instance-access and using the RSA key to copy the logs via scp command. However, I cannot use it anymore due to GetInstanceAccess being deprecated for fleets that use SDK 5 or higher. I managed to get credentials via get-compute-access, but the format is invalid for SSH connection.

The documentation still refers to GetInstanceAccess, so I cannot find information on the proper use of GetComputeAccess.

A little update on the issue: I also tried to upload my build to AWS, setting the --server-sdk-version to 5.0.3, and to create a fleet using that build, but it fails as well. I'm still waiting to get some logs to check the reason (fleet has been ACTIVATING for over 30min now, and I can get logs while it's in this state).

Is it related to GameLiftLocal being still on an old version of the Server SDK and not compatible with 5.0.3?

Yes, GameLiftLocal is only supported for SDK versions pre-5.x

I managed to get credentials via get-compute-access, but the format is invalid for SSH connection.

Hey Bnnoy,

The standard for SDK 5 fleets is to use SSM. Check out the answer to this question for guidance while we work on updating the documentation: https://repost.aws/questions/QUKtsf6-brR4yhhYTL1Taniw/connect-to-windows-server-2016-gamelift-instance-with-sdk-version-5#ANhWlxD6VdQEaEEROOLc1UMg