InterSystems Developer Community

🤠 If you're running InterSystems IRIS across multiple servers, you've probably felt this pain: something goes wrong, and you have to log into each production instance one by one to find the message you're looking for.

Enterprise Message Bank solves exactly that. You set up one central server, add a single operation to each of your client productions, and from that point on — all messages and logs from every instance flow into one place. One search, everything visible.

The article walks through a working Docker example with three containers: a message bank server and two client productions. Every config setting, every line of ObjectScript source code is included — including an optional Helper Class if you need to customize how messages are stored or described 😄

Read the full setup guide 👇
https://community.intersystems.com/post/how-implement-enterprise-message-bank

🤠 If you're running InterSystems IRIS on AWS and wondering how to lock it down properly, Roy Leonov just published a guide that walks through exactly that.

The architecture covers five layers: perimeter filtering with AWS WAF and CloudFront, network isolation with private VPC subnets and Kubernetes network policies, API security with InterSystems IAM including rate limiting and session management, Web Gateway hardening with Nginx URI whitelisting and security headers, and database-level protection with TLS encryption, non-root ex*****on, and AES-256 encryption at rest.

The practical part: all five layers together add only 20–30ms of average latency and the system handles over 2,000 requests per second. The article has been marked as an InterSystems Data Platform Best Practice 😄
Read the full guide 👇
https://community.intersystems.com/post/multi-layered-security-architecture-iris-deployments-aws-intersystems-iam