We are currently setting up some authentication systems for our UE4 game servers so that we are sure they are the only devices/users that are capable of accessing our internal API / LAMDBA functions.
With that in mind, there is a desire to not hard code any COGNITO user ID's or tokens into the actual server-code itself. Instead, we would like to pursue having these tokens be generated and cycled through on AWS's side, to keep it decoupled. We are undecided whether these tokens should be for the life of the Gamelift server or for a set period of time—whichever is most feasible. This way, if we need to adjust access to certain features down the road, it will not require an update to the deployed Unreal Engine server build.
Does AWS API or LAMDBA have any features out of the box to check if an API request is coming from within AWS, ideally from one of the active Gamelift instances?
While we may still need to create a COGNITO identity for the servers, or just check the local IP of the running Gamelift servers, the ideal flow would look like:
-
UE4 game server on AWS asks for a token on Startup.
-
LAMDBA Authorization script checks to make sure it is valid and coming from within AWS/Gamelift
-
Once Validated, LAMDBA function provides a token to enable server to use in backend LAMDBA functions.
-
Before Gamelift Server shutdown, revoke access or add to a "black-listed" token Database to prevent second use before token expiration.
AWS OFFICIALUpdated a year ago