Failing to start ConsoleMe

[netflix]

Failing to start ConsoleMe

[castrapel]

Thank you for this issue!

I think this is because you're deploying to a region that isn't considered your "active region" in ConsoleMe.

Since ConsoleMe's celery tasks don't want to exhaust your rate limits by querying IAM, AWS config, and other services in every one of your regions, we only query in your "active region" as defined in your ConsoleMe configuration under the key: celery.active_region

If you're using this file, try a line like the following to your configuration, substituting us-east-1 for the region you are deploying in. I'd recommend first doing this in your instance and re-running cloud-init to make sure it works:

celery:
  active_region: us-east-1

I will look into modifying the default terraform configuration to have this pre-configured for the region the user is deploying in. A better option might be to always default the active region to the current region consoleme is deployed in, if it is left unconfigured.

[yi2020]

For reference, this is what I'm working on: #264 (you can see if maybe I broke something in there, especially the user_data)

[yi2020]

@castrapel I'm actually doing everything in us-east-1.

[castrapel]

It looks like we still don't have defaults specified in that Terraform config. I think the fix is to modify terraform/central-account/templates/example_config_terraform.yaml and add those lines:

celery:
  active_region: us-east-1

[castrapel]

Also feel free to join our Discord channel, if it would help I'd be happy to hop on a Zoom with you for some pair debugging. I'd bet we'd get some good notes and fixes in the process:

https://discord.gg/nQVpNGGkYu

[castrapel]

This is fixed in #264 .

Once merged, #8785 will add more enhancements to the flow.