Resource Requirements

For a full deployment you need the following

1. Hardware requirements mentioned below.

2. Public IP assigned to machine if public access is enabled (for public facing portals and apps)

3. Domain names

4. Domain mapping

5. Certificates

Hardware requirements

Configuration	vCPU	RAM	Storage	Notes
Development/ Sandbox	16	64 GB	128 GB SSD	For one environment/sandbox. For more number of sandboxes, scale up proportionately.
Production	64	256 GB	512 GB SSD	Storage will depend on several factors, so option to expand the volume should be available.
Production - Backups			512 GB S3/HDD/SDD/Tape	Only for backups.

• Each VM should have minimum 2 network interface cards for creating access channels

• SSD storage is vital for performance (HDD does not work well).

Domain names

To access resources on cluster, domain names and mappings are required. The suggested domain name convention is as follows:

<module>.<environment>.<organisation>.<tld>

Example:

• spar.dev.openg2p.org

• socialregistry.uat.openg2p.org

Domain mapping

Requirement Description	Domain Name (examples)	Mapped to
Domain mapping to sandbox	dev.openg2p.net uat.openg2p.net staging.openg2p.org	"A" Record mapped to Load Balancer IP (For sandbox, where LB is not used, this can be mapped directly to nodes of the K8s cluster, at least 3 nodes).
Wild card mapping to modules	*.dev.openg2p.net *.uat.openg2p.net *.staging.openg2p.org	"CNAME" Record mapped to the domain of the above "A" record. (This is a wildcard DNS mapping)

The domain name mapping needs to be done on your domain service provider. For example, on AWS this is configured on Route 53.

Certificates

At least one wildcard certificate is required depending on the above domain names used. This can also be generated using Letsencrypt. See guide here.