One of the Systems Administrators has taken a look at the current state of our environment. He has reported that there is a parameter msising in our backend setup. Luckily, we can use AWS Systems Manager to fix this.
It looks like this parameter holds the game session configuration and state. Each time a game Manager creates or ends a session, our Alien Attack game updates this parameter. We need to create and store this parameter in the backend of our environment’s architecture for persistence. Let’s follow the specifications below and use the Systems Manager console to create this new parameter.
What are we fixing? It looks like we are missing a session parameter, which is causing the application to break. The session parameter tells our application about the state of the games that are currently running within the Alien Attack environment. Without it, our application doesn’t know which games to make available to the gamers.
yourenvironmentnameshould be the same name that is being used for the other parameters in your environment. In this case, your Environment Name will be lowercase.)
Existing session (opened or closed)
null(insert the word null all lowercase, Null will not work; make sure there are no spaces before the word).
If your parameter was created successfully, you should get the message “Create parameter request succeeded”. Make sure the parameter exists in your Parameter Store list.
cdk diff -c envname=$envname -c sessionparameter=truein the terminal window. This will show you what will be changed in your environment.
cdk deploy -c envname=$envname -c sessionparameter=trueto deploy the changes.
Great work! Let’s try to log in to the Manager Console one more time.
If you have configured everything correctly, you should be forwarded to the configuration page. It looks like this part of the application is working now.
But wait! Don’t try to play the game yet.
According to our notes, there are a few more pieces of the game that we need to fix.