AWS Sizing

When deploying a self-managed deployment of the JFrog Platform on AWS, it is important to consider the hardware and sizing requirements to ensure optimal performance and scalability.

The following guidelines are recommended for sizing your AWS infrastructure.

Artifactory

NOTES:

Each Artifactory replica should run in its own instance (prefer a dedicated node pool)
Each Nginx replica should run in its own instance (prefer a dedicated node pool)
Distribution can run on the Artifactory nodes

Size Template	Small	Medium	Large	XLarge	2XLarge
Number of Artifactory Replicas	1	2	3	4	6
Number of Nginx Replicas	1	2	2	2	3

Artifactory node pool instance	m8g.2xlarge	m8g.2xlarge	m8g.4xlarge	m8g.4xlarge	m8g.4xlarge
CPU	8	8	16	16	16
Memory	32	32	64	64	64

Nginx node pool instance	c8g.xlarge	c8g.xlarge	c8g.xlarge	c8g.2xlarge	c8g.2xlarge
CPU	4	4	4	8	8
Memory	8	8	8	16	16

PostgreSQL RDS instance	db.m8g.2xlarge	db.m8g.4xlarge	db.m8g.8xlarge	db.m8g.12xlarge	db.m8g.16xlarge
CPU	8	16	32	48	64
Memory	32	64	128	192	256
Max connections	100	200	600	2000	5000

Xray

NOTES:

Each Xray replica should run in its own instance (prefer a dedicated node pool)
Xray has HPA enabled, so more instances should be available if needed
If running JAS, it’s recommended to use a dedicated node pool for it to protect Xray and Artifactory pods

Size Template	Small	Medium	Large	XLarge	2XLarge
Number of Xray Replicas	1	1	1	2	3

Xray node pool instance	c8g.2xlarge	m8g.2xlarge	m8g.2xlarge	m8g.2xlarge	m8g.2xlarge
CPU	8	8	8	8	8
Memory	16	32	32	32	32

JAS node pool instance	m8g.2xlarge	m8g.2xlarge	m8g.2xlarge	m8g.2xlarge	m8g.2xlarge
CPU	8	8	8	8	8
Memory	32	32	32	32	32

PostgreSQL RDS instance	db.m8g.xlarge	db.m8g.2xlarge	db.m8g.4xlarge	db.m8g.8xlarge	db.m8g.12xlarge
CPU	4	8	16	32	48
Memory	16	32	64	128	192
Max connections	200	500	600	1200	2000

Storage

See Storage Specifications for details on storage requirements and recommendations.