Skip to main content

AWS Marketplace quick help

This page is a one-page checklist for installing and operating the Patient Journey Intelligence container product from AWS Marketplace on Amazon EKS. For full details, follow the installation guide.

Installation guide · AWS Marketplace listing · Support: support@johnsnowlabs.com

Install from AWS Marketplace​

  1. Subscribe in AWS Marketplace, then obtain the release-supplied installer and matching updater, the published chart tag, and the listing product code. Repository templates lack the required build-injected secret.

  2. Use a Linux terminal with Bash 4+, AWS CLI v2, kubectl, Helm 3.10+, eksctl, jq, OpenSSL, and GNU utilities. Configure AWS credentials and the required permissions.

  3. In a dedicated working directory, replace the product-code placeholder and run the installer. You can also omit --product-code to enter the code interactively:

    chmod 700 marketplace-installer.sh
    ./marketplace-installer.sh --product-code "<listing-product-code>" --time

  4. Confirm the AWS account, then choose the region, a new or existing EKS cluster, the namespace (default pji), the chart tag, and the base URL. A blank URL uses the nginx LoadBalancer address over HTTP.

  5. The installer configures the scheduler's metering role automatically. Verify its IRSA annotation, then check readiness. No separate API Marketplace role attachment is required.

  6. Sign in as admin using ./credentials.txt and complete onboarding.

The installer sets up storage, CSI drivers, nginx ingress, ECK, and the Helm release pj-app. Review the existing-cluster limitations, including the fixed scheduler IAM role name and the ingress-nginx retirement.

--modes selects product modes, and --enable-naaccr-services requires matching optional image artifacts. These flags do not add services that are unavailable in the Marketplace release. --dry-run requires live access, changes local files, and may fail before completing.

Operate the deployment​

  • Security: configure HTTPS before sensitive or production use. New EFS filesystems are encrypted; EBS encryption depends on the region setting. Vault and then remove credentials.txt, and restrict access to Secrets, Helm data, and the installer. Secure the seeded demo and john accounts. See security and rotation.
  • Health and metering: check helm status pj-app -n <namespace> and kubectl get pods,pvc,ingress -n <namespace>. A healthy deployment has ready workloads, Bound PVCs, a working login, and successful hourly Marketplace task reports. See monitoring.
  • Upgrade: back up data and preserve secrets, then use the release-specific instructions. Do not rerun the first-install script.
  • Uninstall: run helm uninstall pj-app -n <namespace>. Storage and AWS or cluster resources can remain and incur charges; follow the cleanup instructions. Subscription cancellation is a separate step.