You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| global.secrets.auth.auth0.secretName | string |`"platform-auth0"`| Auth0 credentials secret name |
324
+
| global.secrets.auth.entra.secretName | string |`"platform-entra"`| Microsoft Entra ID credentials secret name |
325
+
| global.secrets.auth.keycloak.secretName | string |`"platform-keycloak"`| Keycloak credentials secret name |
326
+
| global.secrets.storage.aws_s3.secretName | string |`"platform-aws-s3"`| AWS S3 credentials secret name (not required when services use IAM role access — see Storage Provider Configuration)|
#### Using IAM roles instead of static credentials (IRSA)
656
+
657
+
If you run on EKS and authenticate via IAM Roles for Service Accounts (IRSA) — or any other IAM identity-based mechanism such as an instance profile — you do not need to provide an access key / secret access key, and the `platform-aws-s3` secret is not required.
658
+
659
+
Set `awsS3UseIamRole` (governance-service) and/or `integrityAppBlobStoreAwsUseIamRole` (integrity-service) to `true`. This omits the `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` env vars and the secret reference entirely, so the AWS SDK falls back to its default credential chain. Annotate each service's service account with the role ARN:
With IAM roles in use, leave `global.secrets.storage.aws_s3` unset (or `global.secrets.create: false`) — no S3 credentials secret will be created or referenced.
| config.awsS3UseIamRole | bool |`false`| Use the IAM role credential chain (IRSA/instance profile) instead of static keys; omits the credential env vars and the platform-aws-s3 secret reference |
467
468
468
469
**Azure Blob Storage (only used when storageProvider is "azure_blob"):**
0 commit comments