I'm giving up fighting seed ``` ERROR: Failed to r...
# seed
k
I'm giving up fighting seed
Copy code
ERROR: Failed to run: CDK_DISABLE_VERSION_CHECK=true SEED_UPDATE_CDK_ASSETS=.build/cdk.out cdk deploy --app .build/cdk.out --all --require-approval never --no-color --verbose
Copy code
====================
šŸš€ Deploy
====================
$ cd /tmp/seed/source
INFO: before_deploy hook not found. You can define it in your build spec.
INFO: Learn more about adding a build spec - seed.run/docs/adding-a-build-spec
INFO: Publishing assets...
3.90 s
$ CDK_DISABLE_VERSION_CHECK=true SEED_UPDATE_CDK_ASSETS=.build/cdk.out cdk deploy --app .build/cdk.out --all --require-approval never --no-color --verbose
CDK toolkit version: 2.20.0-seed.1 (build 44f4769)
Command line arguments: {
  _: [ 'deploy' ],
  app: '.build/cdk.out',
  a: '.build/cdk.out',
  all: true,
  'require-approval': 'never',
  requireApproval: 'never',
  color: false,
  verbose: 1,
  v: 1,
  disableVersionCheck: 'true',
  lookups: true,
  'ignore-errors': false,
  ignoreErrors: false,
  json: false,
  j: false,
  debug: false,
  ec2creds: undefined,
  i: undefined,
  'version-reporting': undefined,
  versionReporting: undefined,
  'path-metadata': true,
  pathMetadata: true,
  'asset-metadata': true,
  assetMetadata: true,
  'role-arn': undefined,
  r: undefined,
  roleArn: undefined,
  staging: true,
  'no-color': false,
  noColor: false,
  'build-exclude': [],
  E: [],
  buildExclude: [],
  ci: true,
  execute: true,
  force: false,
  f: false,
  parameters: [ {} ],
  'previous-parameters': true,
  previousParameters: true,
  logs: true,
  '$0': '/usr/local/bin/cdk'
}
merged settings: {
  versionReporting: true,
  pathMetadata: true,
  output: 'cdk.out',
  app: '.build/cdk.out',
  context: {},
  debug: false,
  assetMetadata: true,
  requireApproval: 'never',
  toolkitBucket: {},
  staging: true,
  bundlingStacks: [ '*' ],
  lookups: true
}
Toolkit stack: CDKToolkit
Setting "CDK_DEFAULT_REGION" environment variable to us-east-1
Resolving default credentials
Looking up default account ID from STS
Unable to determine the default AWS account: InvalidClientTokenId: The security token included in the request is invalid.
    at Request.extractError (/usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/protocol/query.js:50:29)
    at Request.callListeners (/usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/request.js:686:14)
    at Request.transition (/usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/request.js:688:12)
    at Request.callListeners (/usr/local/lib/node_modules/@seed-run/aws-cdk/node_modules/aws-sdk/lib/sequential_executor.js:116:18) {
  code: 'InvalidClientTokenId',
  time: 2022-04-26T17:23:37.219Z,
  requestId: 'c81934ae-f798-441f-8b30-65eaac4129eb',
  statusCode: 403,
  retryable: false,
  retryDelay: 238.85488757039616
}
context: {
  'aws:cdk:enable-path-metadata': true,
  'aws:cdk:enable-asset-metadata': true,
  'aws:cdk:version-reporting': true,
  'aws:cdk:bundling-stacks': [ '*' ]
}
Failed to store notices in the cache: Error: ENOENT: no such file or directory, open '/root/.cdk/cache/notices.json'
Notices refreshed
--app points to a cloud assembly, so we bypass synth
✨  Synthesis time: 0.06s
prod-file-builder-saas-my-stack: deploying...
 āŒ  prod-file-builder-saas-my-stack failed: Error: Need to perform AWS calls for account my-account, but no credentials have been configured
    at SdkProvider.forEnvironment (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/api/aws-auth/sdk-provider.ts:179:46)
    at CloudFormationDeployments.prepareSdkFor (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/api/cloudformation-deployments.ts:437:22)
    at CloudFormationDeployments.deployStack (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/api/cloudformation-deployments.ts:333:70)
    at CdkToolkit.deploy (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/cdk-toolkit.ts:209:24)
    at initCommandLine (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/cli.ts:342:12)
Failed to store notices in the cache: Error: ENOENT: no such file or directory, open '/root/.cdk/cache/notices.json'
Failed to get tree.json file: Error: cdk.out/tree.json: ENOENT: no such file or directory, open 'cdk.out/tree.json'
Need to perform AWS calls for account my-account, but no credentials have been configured
Error: Need to perform AWS calls for account my-account, but no credentials have been configured
    at SdkProvider.forEnvironment (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/api/aws-auth/sdk-provider.ts:179:46)
    at CloudFormationDeployments.prepareSdkFor (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/api/cloudformation-deployments.ts:437:22)
    at CloudFormationDeployments.deployStack (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/api/cloudformation-deployments.ts:333:70)
    at CdkToolkit.deploy (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/cdk-toolkit.ts:209:24)
    at initCommandLine (/usr/local/lib/node_modules/@seed-run/aws-cdk/lib/cli.ts:342:12)
ERROR: Failed to run: CDK_DISABLE_VERSION_CHECK=true SEED_UPDATE_CDK_ASSETS=.build/cdk.out cdk deploy --app .build/cdk.out --all --require-approval never --no-color --verbose
l
This looks like enough of an explaination to me:
Error: Need to perform AWS calls for account my-account, but no credentials have been configured
Did you set up the AWS IAM Info properly in the app's Settings?
k
Yes, I have even reentered my credentials again in seed project settings
My connected github repo is private but would there be a difference with public repo?
l
Nope, as long as you set the correct auth it's gonna pull from it like you do locally
k
OK, my credentials were wrong. My mistake