Infrastructure requirements

Edit on GitHub

To mitigate security risks, this article describes the system infrastructure requirements for Spryker Marketplace projects. When you host your Spryker application in SCCOS, these requirements will be configured for you out of the box. If your system infrastructure (cloud PaaS or on-premise) is managed, you must ensure these security requirements are met.

Applications resources visibility

This section contains details about the visibility of the resources in the network

MerchantPortal PrimaryDatabase, QueueBroker, MerchantPortalSessionStorage yes
Backoffice PrimaryDatabase, QueueBroker, BackofficeSessionStorage no, accessed through VPN
Scheduler PrimaryDatabase, QueueBroker, Storage, Search no, accessed through a Bastion
Glue Storage, Search, Gateway yes
Yves Storage, Search, Gateway yes

This diagram illustrates how visibility of resources relates to private and public network relationships:

Entity diagram

Merchant Portal endpoints whitelisting

Merchant Portal is exposed to WAN and MUST NOT provide any Gateway or Backoffice facilities.

In the webserver configuration (AWS WAF can also be used), only HTTP endpoints of the MerchantPortalGui should be allowed. Their prefix is all the same (/domain-merchant-portal-gui).

/^[a-zA-Z-]+-merchant-portal-gui.* - use this pattern as a whitelist in Nginx (or WAF) configuration.

Merchant portal network

In order for the Merchant Portal to function properly, it should be in a dedicated public network (not the same network where Yves/Glue runs) with access to a network Database and QueueBroker (see diagram above).

Firewall rules for the Merchant Portal (NACLs or Security groups)

To properly configure Merchant Portal firewall, use these rules:

SG / NACLs Merchant Portal Redis(session):6379 Allow
NACLs Redis(session):6379 Merchant Portal Allow
SG / NACLs Merchant Portal RDS:3306 Allow
NACLs RDS:3306 Merchant portal Allow
SG / NACLs Merchant Portal RabbitMQ:5672 Allow
NACLs RabbitMQ:5672 Merchant Portal Allow
SG / NACLs Nginx Merchant portal:900x Allow
NACLs Merchant Portal:9001 Nginx Allow
Default rule any Merchant Portal Deny
  • Security groups and host-based firewalls must also implement “allow” rules for Merchant portal on Redis, RDS, Rabbit MQ, and Nginx sides.
  • In addition, depending on the monitoring system used, “allow” rules will need to be implemented as well.

Database (MariaDb/Mysql/Postgres)

Each database user must have dedicated user credentials:

Scheduler FULL ADMIN [Create schema, create tables, drop tables, create users, etc]
Gateway CRUD for the tables
MerchantPortal CRUD for the tables related to MerchantPortal. By default the same as Gateway

Each application must have the following user rights:

GLUE Read-only
Yves Read-only
Scheduler Read-write
Merchant Portal none