Apollo S3 with IRSA / ServiceAccount credentials needs no static S3 secret keys
For IRSA / ServiceAccount-based S3 access,S3_ACCESS_KEY_ID and S3_SECRET_ACCESS_KEY should not be populated in the Apollo container. These secret keys are optional. If the keys are removed from composio-composio-secrets, Apollo can fall back to the configured pod ServiceAccount / AWS SDK credential chain.
Do not set placeholder S3 credential values for IRSA deployments. Values such as dummy-value or a literal string null are treated as credentials and can make S3 pre-signed URLs fail with provider errors such as:
S3_ACCESS_KEY_ID and S3_SECRET_ACCESS_KEY are not present with dummy/static values in Apollo’s runtime environment.
Example response:
Disable social login explicitly for self-hosted deployments
NEXT_PUBLIC_DISABLE_SOCIAL_LOGIN controls whether social login buttons such as Google/GitHub appear on the frontend login page. For self-hosted customers that should hide social login, set the Helm values override as a string: