Migration

CloudSuite Industrial Single-Tenant Deployment Setup

CloudSuite Industrial single-tenant (ST) deployments provide dedicated AWS infrastructure for organizations requiring full database access, custom upgrade scheduling, and regulatory isolation. ST is the preferred model for enterprises with complex customizations, strict compliance requirements (ITAR, FedRAMP), or high-volume batch processing that exceeds MT performance tiers. This guide covers the complete ST provisioning process and configuration options.

Dedicated Infrastructure Provisioning

In ST mode, Infor provisions a dedicated AWS account with isolated VPC, dedicated RDS instances, and tenant-specific EC2 or EKS clusters. The customer receives direct SQL Server or PostgreSQL access to their CSI database, enabling custom stored procedures, reporting views, and direct integration queries that are prohibited in MT. Infrastructure sizing is determined during the Solution Design phase where Infor architects map your current on-premise SyteLine resource consumption to equivalent AWS instance types.

  • Dedicated AWS account with isolated VPC, subnets, and NAT gateways for complete network segregation
  • Direct database access via SQL Server Management Studio or pgAdmin for custom queries and stored procedures
  • Infrastructure sizing based on Solution Design mapping: CPU cores, RAM, IOPS from on-premise SyteLine metrics
  • Dedicated EKS cluster for CSI application pods with customer-controlled scaling policies and node groups
  • Optional VPN or AWS Direct Connect for secure network connectivity between on-premise systems and ST environment

Upgrade Scheduling and Customization Freedom

Single-tenant customers control their upgrade timeline within Infor's supported version window (typically N-2 releases). Upgrades are coordinated through Infor Xtreme case management with a dedicated CloudOps engineer assigned to your tenant. ST allows assembly-level customizations, custom Mongoose forms, stored procedure overrides, and direct IDO modifications that would break MT compatibility. However, Infor still recommends using the extensibility framework to minimize upgrade friction.

  • Customer-controlled upgrade scheduling within the N-2 supported version window (approximately 18-month range)
  • Dedicated CloudOps engineer for upgrade coordination, testing support, and rollback procedures
  • Assembly-level customizations (.NET DLLs) deployable to the ST application tier via Infor Deployment Manager
  • Custom Mongoose forms with modified IDO mappings deployed without affecting other tenants or upgrade paths
  • Pre-upgrade testing environment (sandbox) provisioned automatically 30 days before scheduled upgrade windows

Security and Compliance Configuration

ST deployments support enhanced security configurations including customer-managed encryption keys (CMK) via AWS KMS, dedicated HSM modules for FIPS 140-2 compliance, and custom WAF rules on the application load balancer. For regulated industries, ST provides the isolation required for ITAR, FedRAMP Moderate, and SOC 2 Type II compliance where shared infrastructure models cannot satisfy auditor requirements.

  • Customer-managed encryption keys (CMK) via AWS KMS for data-at-rest encryption on RDS and S3 resources
  • Dedicated CloudHSM modules available for FIPS 140-2 Level 3 compliance in defense and government sectors
  • Custom AWS WAF rules on the ALB for application-layer firewall policies specific to your security requirements
  • SOC 2 Type II audit support with dedicated infrastructure evidence collection and access log segregation
  • ITAR compliance configuration with GovCloud region deployment option for defense manufacturing customers

Evaluating single-tenant vs multi-tenant for your CSI deployment? Let Netray architects help you map requirements to the right deployment model.