s3 remote error: Could not find API configuration s3-2006-03-01

mavoff

Hi all,

We're using XO from sources and recently I was reading the archives regarding the beta feature of using s3 as remote.

I tried to add but I get this error:

remote.test
{
  "id": "faa61193-495c-4ec1-be84-8c64040dde5b"
}
{
  "message": "Could not find API configuration s3-2006-03-01",
  "code": "MODULE_NOT_FOUND",
  "requireStack": [
    "/opt/xen-orchestra/node_modules/aws-sdk/clients/s3.js",
    "/opt/xen-orchestra/node_modules/aws-sdk/clients/all.js",
    "/opt/xen-orchestra/node_modules/aws-sdk/lib/aws.js",
    "/opt/xen-orchestra/node_modules/@sullux/aws-sdk/index.js",
    "/opt/xen-orchestra/@xen-orchestra/fs/dist/s3.js",
    "/opt/xen-orchestra/@xen-orchestra/fs/dist/index.js"
  ],
  "time": "2022-04-01T12:13:38.065Z",
  "originalError": {
    "code": "MODULE_NOT_FOUND",
    "requireStack": [
      "/opt/xen-orchestra/node_modules/aws-sdk/clients/s3.js",
      "/opt/xen-orchestra/node_modules/aws-sdk/clients/all.js",
      "/opt/xen-orchestra/node_modules/aws-sdk/lib/aws.js",
      "/opt/xen-orchestra/node_modules/@sullux/aws-sdk/index.js",
      "/opt/xen-orchestra/@xen-orchestra/fs/dist/s3.js",
      "/opt/xen-orchestra/@xen-orchestra/fs/dist/index.js"
    ],
    "message": "Cannot find module '../apis/s3-2006-03-01.min.json'
Require stack:
- /opt/xen-orchestra/node_modules/aws-sdk/clients/s3.js
- /opt/xen-orchestra/node_modules/aws-sdk/clients/all.js
- /opt/xen-orchestra/node_modules/aws-sdk/lib/aws.js
- /opt/xen-orchestra/node_modules/@sullux/aws-sdk/index.js
- /opt/xen-orchestra/@xen-orchestra/fs/dist/s3.js
- /opt/xen-orchestra/@xen-orchestra/fs/dist/index.js"
  },
  "name": "MODULE_NOT_FOUND",
  "stack": "MODULE_NOT_FOUND: Could not find API configuration s3-2006-03-01
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.get [as 2006-03-01] (/opt/xen-orchestra/node_modules/aws-sdk/clients/s3.js:11:17)
    at Object.apiLoader (/opt/xen-orchestra/node_modules/aws-sdk/lib/api_loader.js:5:33)
    at Function.defineServiceApi (/opt/xen-orchestra/node_modules/aws-sdk/lib/service.js:795:22)
    at features.constructor.getLatestServiceClass (/opt/xen-orchestra/node_modules/aws-sdk/lib/service.js:122:19)
    at features.constructor.loadServiceClass (/opt/xen-orchestra/node_modules/aws-sdk/lib/service.js:112:19)
    at features.constructor.Service [as constructor] (/opt/xen-orchestra/node_modules/aws-sdk/lib/service.js:47:29)
    at new features.constructor (/opt/xen-orchestra/node_modules/aws-sdk/lib/util.js:629:24)
    at construct (/opt/xen-orchestra/node_modules/@sullux/aws-sdk/index.js:241:13)
    at Object.NodeHttpHandler [as s3] (/opt/xen-orchestra/node_modules/@sullux/aws-sdk/index.js:246:26)
    at new S3Handler (/opt/xen-orchestra/@xen-orchestra/fs/src/s3.js:66:27)
    at getHandler (/opt/xen-orchestra/@xen-orchestra/fs/src/index.js:28:10)
    at _class2.getRemoteHandler (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/remotes.mjs:73:17)
    at _class2.testRemote (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/remotes.mjs:97:11)
    at Api.callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:307:20)"
}

XO is up to date
xo-server 5.89.0 xo-web 5.95.0

Thank you

Danp

Hi @maverick,

I'm not sure if it will have any effect, but you should update to the latest source and then test it again.

Dan

olivierlambert

Does it ring any bell @florent ?

florent

@maverick Hi maverick, did you also update the packages ? We did move from aws-sdk2 to aws sdk 3 recently

mavoff

Hi guys thank you for the feedback, but I guess I'm a bit lost here.

So usually when I update XO I go to the xen-orchestra folder and do:

git checkout .
git pull --ff-only
yarn
yarn build

The branch I'm in:

# git rev-parse --abbrev-ref HEAD
master

How should I update the packages? thank you.

mavoff

@florent this is what I have

$ ls -la node_modules/ | grep aws
drwxrwxr-x.    3 root root    121 Dec  8 14:04 aws4
drwxr-xr-x.   10 root root    153 Mar 31 14:46 @aws-crypto
drwxr-xr-x.   78 root root   4096 Mar 31 14:46 @aws-sdk
drwxrwxr-x.    2 root root     74 Dec  8 14:04 aws-sign2

mavoff

Ok so i created a symlink from @aws-sdk to was-sdk and now it works.
as the error was looking for node_modules/aws-sdk and not node_modules/@aws-sdk