Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | Use these checks to troubleshoot Composio self-hosted or on-prem Helm deployments. |
| 2 | |
| 3 | ## Apollo S3 with IRSA / ServiceAccount credentials needs no static S3 secret keys |
| 4 | |
| 5 | 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. |
| 6 | |
| 7 | 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: |
| 8 | |
| 9 | ```text |
| 10 | InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records. |
| 11 | InvalidToken: The provided token is malformed or otherwise invalid. |
| 12 | ``` |
| 13 | |
| 14 | For AWS IRSA, configure the Apollo ServiceAccount annotation and object storage backend, then leave static S3 credential secret keys absent: |
| 15 | |
| 16 | ```yaml |
| 17 | apollo: |
| 18 | serviceAccount: |
| 19 | enabled: true |
| 20 | name: "composio-apollo" |
| 21 | annotations: |
| 22 | eks.amazonaws.com/role-arn: "arn:aws:iam::<AWS_ACCOUNT_ID>:role/<IAM_ROLE_NAME>" |
| 23 | objectStorage: |
| 24 | backend: "s3" |
| 25 | ``` |
| 26 | |
| 27 | Debug checks: |
| 28 | |
| 29 | ```bash |
| 30 | kubectl exec -n composio deploy/composio-apollo -- env | grep -E "^S3_|^AWS_" |
| 31 | kubectl logs -n composio deploy/composio-apollo --tail=200 |
| 32 | ``` |
| 33 | |
| 34 | If using pod/container credentials, the Helm storage doc says the Kubernetes secret credential section can be skipped. Verify that `S3_ACCESS_KEY_ID` and `S3_SECRET_ACCESS_KEY` are not present with dummy/static values in Apollo's runtime environment. |
| 35 | |
| 36 | Example response: |
| 37 | |
| 38 | ```text |
| 39 | This looks like Apollo is still receiving static S3 credential env vars, so the AWS SDK is using those instead of falling back to the ServiceAccount/IRSA credentials. |
| 40 | |
| 41 | For IRSA, `S3_ACCESS_KEY_ID` and `S3_SECRET_ACCESS_KEY` should be absent from the Apollo container. Those secrets are optional; if you remove those keys from `composio-composio-secrets`, Apollo should use the configured ServiceAccount. Placeholder values like `dummy-value` or literal `null` are treated as real credentials and can cause S3 signing errors such as `InvalidAccessKeyId` or `InvalidToken`. |
| 42 | |
| 43 | The immediate fix is to remove `S3_ACCESS_KEY_ID` and `S3_SECRET_ACCESS_KEY` from `composio-composio-secrets`, then confirm the Apollo pod environment no longer includes those values. |
| 44 | ``` |
| 45 | |
| 46 | ## Disable social login explicitly for self-hosted deployments |
| 47 | |
| 48 | `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: |
| 49 | |
| 50 | ```yaml |
| 51 | apollo: |
| 52 | nextPublicDisableSocialLogin: "true" |
| 53 | ``` |
| 54 | |
| 55 | This makes the generated Apollo ConfigMap render an explicit value instead of an empty/null value and should remove repeated ArgoCD diffs immediately. |
| 56 | |
| 57 | Customers can apply the override directly to unblock the deployment. |
| 58 | |
| 59 | Example response: |
| 60 | |
| 61 | ~~~text |
| 62 | `NEXT_PUBLIC_DISABLE_SOCIAL_LOGIN` controls whether the Google/GitHub social login buttons show up on the frontend login page. For your setup, I'd set it explicitly to `"true"` in the Helm values override: |
| 63 | |
| 64 | ```yaml |
| 65 | apollo: |
| 66 | nextPublicDisableSocialLogin: "true" |
| 67 | ``` |
| 68 | |
| 69 | This should make the generated Apollo ConfigMap render the explicit value and stop ArgoCD from diffing null vs empty string immediately. |
| 70 | |
| 71 | The override above can be applied directly; no release-specific promise is required. |
| 72 | ~~~ |