You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 17, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: docs/autostarting.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,8 +91,8 @@ firewall rules to permit worker instances access. This is documented in the abov
91
91
If installing on the `localhost` of the scheduler instance, you will need to install Redis on the instance (this is complete if following the quickstart guide).
92
92
93
93
### Celery Configuration
94
-
You will need to modify the `celeryconfig.py` file that is stored in the base Security Monkey location
95
-
at `/usr/local/src/security_monkey/celeryconfig.py`(https://github.com/Netflix/security_monkey/blob/develop/celeryconfig.py).
94
+
You will need to modify the `security_monkey/celeryconfig.py` file that is stored in the base Security Monkey location
95
+
at `/usr/local/src/security_monkey/security_monkey/celeryconfig.py`(https://github.com/Netflix/security_monkey/blob/develop/security_monkey/celeryconfig.py).
96
96
97
97
This file looks like this:
98
98
```
@@ -153,7 +153,7 @@ The workers are instances that fetch data from your configured accounts. These a
153
153
154
154
You are able to deploy as many workers as you like for your environment. Security Monkey splits up tasks based on the account and technology pair.
155
155
156
-
Similar to configuring the Scheduler above, the workers need to have the **same**`celeryconfig.py` as the scheduler. In here, you can optionally configure
156
+
Similar to configuring the Scheduler above, the workers need to have the **same**`security_monkey/celeryconfig.py` as the scheduler. In here, you can optionally configure
157
157
the number of processes that exist within each instance (via the `worker_concurrency` configuration). By default 10 is selected. You can adjust this as necessary. In general, if you would like to
158
158
scale horizontally, you should deploy more worker instances. This will allow for maximum parallelization.
Copy file name to clipboardExpand all lines: docs/tuneworkers.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Create a new Redis cache ([ElastiCache works well](elasticache_directions.md)),
20
20
**Keep note of the endpoint, you'll need this later**.
21
21
22
22
## Create a dedicated Celery configuration
23
-
For this use case, you would have two different [Celery configuration Python](https://github.com/Netflix/security_monkey/blob/develop/celeryconfig.py) files.
23
+
For this use case, you would have two different [Celery configuration Python](https://github.com/Netflix/security_monkey/blob/develop/securitymonkey/celeryconfig.py) files.
24
24
You will need to make note of the following section:
25
25
```
26
26
# This specifies a list of technologies that workers for the above Redis broker should IGNORE.
@@ -36,15 +36,16 @@ In these variables, you will enter in the index name of the technology. For exam
36
36
of the technologies as they appear in the UI.
37
37
38
38
For this use case, we are going to have a dedicated stack of workers (called the `iam` stack) for IAM Roles, and another stack for everything else (called the `main` stack).
39
-
1. Make a copy of `celeryconfig.py`, and call it `mainceleryconfig.py`
40
-
1. In `mainceleryconfig.py`, make a modification to the `security_monkey_watcher_ignore` variable such that its value is:
39
+
1. Make a copy of `security_monkey/celeryconfig.py`, and call it `security_monkey/mainceleryconfig.py`
40
+
1. In `security_monkey/mainceleryconfig.py`, make a modification to the `security_monkey_watcher_ignore` variable such that its value is:
41
41
```
42
42
security_monkey_watcher_ignore = set(['iamrole'])
43
43
```
44
44
1. Save the file.
45
45
46
46
Next, you will need to make it so that your scheduler and corresponding set of workers that will load this configuration. There is a new environment variable
47
47
that Security Monkey will check to properly load this configuration: `SM_CELERY_CONFIG`. For this stack, `SM_CELERY_CONFIG` needs to be set to: `"mainceleryconfig.py"`.
48
+
(Do not place `security_monkey` in the variable name...just call it the destination name of the file that resides within the `security_monkey/` python code location -- this is the same place that `manage.py` lives)
48
49
Because we utilize `supervisor`, you will need to add this to the `environment` section. Here are sample configurations:
0 commit comments