What is difference between "Concurrent processes" and "Game session activation"?

GameSessions don't "activate" as soon as the instance is done starting, only when CreateGameSession is called. The "activation" settings limit how often activations can be used, which is useful if starting 10+ GameSession on the same instance will cause CPU to spike or if you have creating game session able to be called directly from the client.

I got it. I have one more question. I think "Game session activation" is good for server. So I can choose "No limit" for the Game session activation but why can I set up limit of the Game session activation per instance. Maybe GameLift will intelligently use it if I choose "No limit".

REMOVEDUPLOAD

That field is ignored if you don't choose that option