Elastic Path Account Management Deployment Guide

Technical Requirements

Technical Requirements

Infrastructure Requirements

Requirement Usage
New DNS records
  • For accessing the Account Management user interface —The primary entry point and landing page for the users. This domain name is visible to end-users.
  • For accessing the Account Management API — The Hypermedia REST endpoints that are used by the user interface, store fronts, and touch points. This domain name is not typically visible to users, but developers and system administrators may access Account Managementstudio using this domain name.
  • For accessing Keycloak — This service is responsible for handling login of all users, and so the domain name will be visible to users.
Three SSL certificates For the Account Management user interface, Account Management API , and Keycloak.
SMTP-compatible server Users will be required to receive e-mails that are sent by Keycloak, in order to create accounts. You may use a service like Amazon Simple Email Service (SES). You must configure the name and the e-mail address to use when sending e-mails to the buyer divisions.
MySQL compatible server For Account Management data storage. Elastic Path supports the following services:
  • MySQL 5.7 on Amazon RDS
  • Amazon Aurora RDS (MySQL 5.6-compatible)
A computer connected to the MySQL server with Liquibase 3.5.5 and the MySQL connector 8.0.13 For initializing the schema using liquibase. You can use a local machine or a hosted machine within AWS.
A computer with Docker installed For building docker containers.
JWT RS256 private and public key pair To enable secure communication between Elastic Path Commerce and the Account Management service. We recommend using openssl to generate the key, but you can use any mechanism to generate the key so long as it is an RS256 key.