Deploy to AWS stack cloudformatting

Local Setup
1

using (nakama stack)[AWS Marketplace: Nakama] from aws marketplace
the stack is building without any errors until it stops on NakamaService CREATE_IN_PROGRESS Resource creation Initiated after some time it crashes with a timeout error
I didn’t upload my runtime model or config.yml yet

  1. Versions: Nakama {3.10.0}, {aws cloudformatting}
2

Hello @Kareem21227gg

Do you have any logs that you could provide us and could explain how you are deploying it? The more information you provide, the better we can help.

3

Hi @flavio
there is no log cause i couldn’t start the ecs yet (which where the problem happen)

Usage Instructions for 3.10.0

  1. Run the CloudFormation wizard located here: https://console.aws.amazon.com/cloudformation/home?#/stacks/quickcreate?templateURL=https://nakama-awsmp.s3.amazonaws.com/stack-m1.yaml&param_NakamaVersion=3.10.0
  2. When the stack is completed it will produce 2 outputs: one is the URL of the Nakama console of your newly created instance and the other is the S3 bucket in to the root of which you can put your config.yaml and any Nakama runtime plugins.
  3. After you modify config.yaml or plugins you need to locate the running nakama ECS tasks in the AWS Console and restart them to apply the new configuration and runtime.

step one is where the problem happen so i assumed that there is something wrong with the stack templet

4

@flavio I have the same issue as Kareem. I created a flesh AWS root account, then created a IAM user with all administrative rights, and then under that IAM user, I subscribed to Nakama 3.10.0. The deployment halted at initialising NakamaService, which eventually timed out and rolled back without much helpful info:
NakamaService: Resource timed out waiting for completion (RequestToken: XXXX)
NakamaService: The following resource(s) failed to create: [NakamaService]. Rollback requested by user.

I tried all available Nakama version and the recent one failed in the same way. The older version failed earlier, some complaining malformed variable name, e.g. for S3 bucket, etc.

5

what I did was deploying to ecs
cloudformatting didn’t work for me

1 Like