-
Notifications
You must be signed in to change notification settings - Fork 4
/
docker-compose.yaml
80 lines (69 loc) · 3.02 KB
/
docker-compose.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
services:
cloud-scanner:
container_name: deepfence-cloud-scanner
image: ${IMAGE_REPOSITORY:-quay.io/deepfenceio}/cloud_scanner_ce:${DF_IMG_TAG:-2.4.0}
restart: unless-stopped
environment:
# Deepfence management console url and port
# Format: deepfence.customer.com or 123.123.123.123
MGMT_CONSOLE_URL: ""
MGMT_CONSOLE_PORT: 443
# Get Deepfence api key from UI -> Settings -> User Management
DEEPFENCE_KEY: ""
# aws / gcp / azure
CLOUD_PROVIDER: ""
CLOUD_REGION: ""
# AWS account ID / GCP project ID / Azure subscription ID to monitor
CLOUD_ACCOUNT_ID: ""
# Optional: AWS account ID / GCP project ID / Azure subscription ID where the helm chart is deployed,
# in case it is different from cloudAccount.accountID
DEPLOYED_ACCOUNT_ID: ""
# Account name (Optional, for easy identification. Not required in organization deployment.)
CLOUD_ACCOUNT_NAME: ""
# For Organization deployment:
# Is this organization deployment or single account deployment?
ORGANIZATION_DEPLOYMENT: false
# Organization root account ID
# Should be same as cloudAccount.accountID, in case of AWS/GCP
# Should be tenant id, in case of Azure
CLOUD_ORGANIZATION_ID: ""
# Applicable only in AWS
# Role name. The name should be same across all accounts in the Organization deployment.
# Role ARN example: arn:aws:iam::123456789012:role/deepfence-cloud-scanner-role
# Role name in this case is deepfence-cloud-scanner-role
ROLE_NAME: ""
# Only applicable in AWS
# Must be one of "Ec2InstanceMetadata", "EcsContainer", "Environment", "ServiceAccount"
# service account needs special handling
AWS_CREDENTIAL_SOURCE: "Ec2InstanceMetadata"
# Optional: To refresh the cloud resources every hour, provide CloudTrail Trail ARNs (Management events with write-only or read-write).
# If empty, a trail with management events will be automatically chosen if available.
CLOUD_AUDIT_LOG_IDS: ""
HTTP_SERVER_REQUIRED: "false"
SUCCESS_SIGNAL_URL: ""
DF_LOG_LEVEL: info
SCAN_INACTIVE_THRESHOLD: "21600"
# Applicable only in AWS
# Policy set for Cloud Scanner in CloudFormation / terraform
# arn:aws:iam::aws:policy/ReadOnlyAccess / arn:aws:iam::aws:policy/SecurityAudit
CLOUD_SCANNER_POLICY: ""
# AZURE_TENANT_ID: ""
# AZURE_REGION: ""
# AZURE_CLIENT_ID: ""
# AZURE_CLIENT_SECRET: ""
# AZURE_SUBSCRIPTION_ID: ""
# Provide base64 encoded Service Account Keys for GCP Scanner
# GCP_SERVICE_ACCOUNT_CREDENTIAL: ""
DEPLOYMENT_MODE: "docker"
HOME_DIR: "/home/deepfence"
DF_INSTALL_DIR: "/data/home/deepfence"
STEAMPIPE_INSTALL_DIR: "/data/home/deepfence/.steampipe"
volumes:
- cloud_scanner_data:/data:rw
logging:
driver: "json-file"
options:
max-size: "50m"
volumes:
cloud_scanner_data:
driver: local