Hi Team, We are deployed Infisical on AWS EKS clu...
# infisical-help
s
Hi Team, We are deployed Infisical on AWS EKS cluster. Earlier we used MongoDB external database and the deployment was working fine. yesterday we upgraded the EKS cluster version and node version, after that infisical was not working and expecting pgsql database instead of MongoDB. We migrated the mongo database to postgres via migrator tool Now we are using https://github.com/Infisical/infisical/blob/main/helm-charts/infisical-standalone-postgres/values.yaml this file as values.yaml for deployment. Now we are stuck at this error Telemetry is enabled (node:1) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023. Please migrate your code to use AWS SDK for JavaScript (v3). For more information, check the migration guide at https://a.co/7PzMCcy (Use
node --trace-warnings ...
to show where the warning was created) {"level":30,"time":1758045987320,"pid":1,"hostname":"infisical-infisical-standalone-infisical-55448c4f85-bw6vn","severity":"INFO","msg":"KMS: Generating ROOT Key"} {"level":50,"time":1758045987321,"pid":1,"hostname":"infisical-infisical-standalone-infisical-55448c4f85-bw6vn","severity":"ERROR","err":{"type":"RangeError","message":"Invalid key length","stack":"RangeError: Invalid key length\n at Cipheriv.createCipherBase (nodeinternal/crypto/cipher121:19)\n at Cipheriv.createCipherWithIV (nodeinternal/crypto/cipher140:3)\n at new Cipheriv (nodeinternal/crypto/cipher243:3)\n at Object.createCipheriv (nodecrypto147:10)\n at Object.encrypt (/backend/src/lib/crypto/cipher/cipher.ts1927)\n at Object.startService (/backend/src/services/kms/kms-service.ts83037)\n at process.processTicksAndRejections (nodeinternal/process/task queues95:5)\n at async registerRoutes (/backend/src/server/routes/index.ts12603)","code":"ERR_CRYPTO_INVALID_KEYLEN"},"msg":"Invalid key length"} We have created a secret using: kubectl create secret generic infisical-secrets \ --from-literal=AUTH_SECRET="$(openssl rand -hex 16)" \ --from-literal=ENCRYPTION_KEY="$(openssl rand -base64 32)" \ --from-literal=JWT_SIGNUP_SECRET="$(openssl rand -hex 32)" \ --from-literal=JWT_REFRESH_SECRET="$(openssl rand -hex 32)" \ --from-literal=JWT_AUTH_SECRET="$(openssl rand -hex 32)" Please let us know the possible solution. We are using this for production env, we are down from yesterday. Expecting quick help Thanks, Shahid