Hi Rakesh
Hardcoding secrets in OperatorConfiguration is strongly discouraged. Use the External Secrets Operator (ESO): install ESO in your cluster, create an ExternalSecret CR that syncs from AWS Secrets Manager to a native Kubernetes Secret, then reference it in your MendixApp CR:
runtime:
envFrom:
- secretRef:
name: mendix-app-secrets
As of Mendix Operator 2.x, the MendixApp CR supports envFrom and env.valueFrom.secretKeyRef natively so ESO is the cleanest fit with no custom patching needed. Alternatively use the AWS Secrets Store CSI driver and mount secrets as a volume with an init container.