@GregS17442473

On client-managed Pega (like your EKS setup), the “Streaming Pega logs to an external Amazon S3 bucket” feature is only documented and supported for Pega Cloud environments managed by Pega, not for self-hosted installs, so there isn’t a one-click, Pega-provided setup you can copy over.  On your own stack, Pega just writes logs via Log4j2 to files / stdout, and it’s your Kubernetes/AWS tooling that should ship those logs into S3. In EKS the usual pattern is: send container logs to CloudWatch (or Fluent Bit / Fluentd), then from there stream or export to S3 using AWS’s standard logging pipelines; Pega doesn’t need to be changed for that. If you really want the app itself to write straight to S3, you’d need to add and configure a custom Log4j appender for S3 (third-party or in-house), point the Pega Log4j2 config at it, and let that handle the S3 upload. Pega doesn’t ship or document such an appender for client-managed environments today, so this falls under general Java/Kubernetes logging best practices rather than Pega-specific docs. In short, the recommended way is to keep Pega logging standard, and let your EKS logging stack (Fluent Bit / CloudWatch Logs / Firehose / S3) handle delivery to S3 per your org’s AWS patterns.