AWS EC2
Use Docker Compose on a regular host on a single EC2 instance, configured with RDS for the metadata database and S3 for file storage.
For new AWS stands the CloudFormation (EKS) or CloudFormation (ECS) templates provision the cluster, RDS, S3, IAM, and load balancers end-to-end — and EKS is the AWS path under active development. This page is for evaluation stands or one-off deployments where you manage the EC2 instance yourself.
Configuration
Follow the Regular machine install instructions, but replace the
GROK_PARAMETERS block on the datagrok service with one that points at your RDS
instance and S3 bucket. If the EC2 instance has an IAM role with S3 access, omit
amazonStorageId and amazonStorageKey — Datagrok resolves credentials from the
instance metadata service.
{
"dbServer": "<RDS_ENDPOINT>",
"dbPort": "5432",
"db": "datagrok",
"dbLogin": "datagrok",
"dbPassword": "<DB_PASSWORD>",
"dbAdminLogin": "<POSTGRES_ADMIN_USER>",
"dbAdminPassword": "<POSTGRES_ADMIN_PASSWORD>",
"amazonStorageRegion": "<AWS_REGION>",
"amazonStorageBucket": "<S3_BUCKET>",
"amazonStorageId": "<AWS_ACCESS_KEY_ID>",
"amazonStorageKey": "<AWS_SECRET_ACCESS_KEY>"
}
For RDS IAM authentication (passwordless DB login), set dbUseIam: true and omit
dbPassword. Datagrok mints SigV4 tokens via the IAM role attached to the EC2 instance.
See Server configuration for the full list of options.
See also
- Regular machine — full Docker Compose install on any host
- AWS CloudFormation (EKS) — recommended AWS path
- AWS CloudFormation (ECS) — Fargate-based AWS deployment
- Components — service list and roles