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
Hi, I have problem in s3 backend with assume role.
Currently, I run commuter by the following command;
git clone [email protected]:nteract/commuter.git
cd commuter
yarn
COMMUTER_S3_ENDPOINT=s3.ap-northeast-1.amazonaws.com COMMUTER_BUCKET=<my_bucket> COMMUTER_STORAGE_BACKEND=s3 yarn dev
The compile succeeds and I get
yarn run v1.21.1
$ npm run build:server
npm WARN lifecycle The node binary used for scripts is /var/folders/c0/rvxcyrm51z395rcx_lg444l00000gn/T/yarn--1578311114367-0.26080746994808/node but npm is using /usr/local/Cellar/node/13.5.0/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
> @nteract/[email protected] build:server /Users/myname/dev_home/commuter
> babel backend -d lib
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade`
Successfully compiled 21 files with Babel.
$ NODE_ENV=development node lib/index.js
CONFIGURED DISCOVERY none
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade`
> Using external babel configuration
> Location: "/Users/myname/dev_home/commuter/babel.config.js"
[ ready ] compiled successfully
[ wait ] compiling ...
[Function: self] { level: 'info', levelIndex: 3, levelRoot: [Circular] }
[ ready ] compiled successfully
However, when I access to localhost:4000, the following log occurs;
Hi, I have problem in s3 backend with assume role.
Currently, I run commuter by the following command;
The compile succeeds and I get
However, when I access to
localhost:4000
, the following log occurs;If I run in production mode,
I get an different error message.
My ~/.aws/config is structured as follows
~/.aws/credentials as follows
And I can successfully run
aws s3 ls
.Any suggestions?
Thank you for your help in advance :)
The text was updated successfully, but these errors were encountered: