ConfigError: Missing region in config #308

richard-smith-sky · 2020-01-17T16:03:16Z

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Bug Report

We have a deployment that relies on serverless-domain-manager which has worked happily for 2 years and then suddenly stopped. It is run locally and remotely on BitBucket Pipelines, which is where we see the failure. Has something changed about the handling of regions? Needless-to-say the region is defined in the serverless configuration.

provider:
  name: aws
  runtime: nodejs12.x
  region: eu-west-2
  tracing: true

>> serverless create_domain -s staging
 
  Error --------------------------------------------------
 
  Error: Error: 'www.mysite.world' was not created in API Gateway.
  ConfigError: Missing region in config
      at createDomainName.catch (/opt/atlassian/pipelines/agent/build/node_modules/serverless-domain-manager/index.js:108:15)
      at <anonymous>
      at process._tickDomainCallback (internal/process/next_tick.js:229:7)
 
     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
 
  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com
 
  Your Environment Information ---------------------------
     Operating System:          linux
     Node Version:              8.17.0
     Framework Version:         1.61.2
     Plugin Version:            3.2.7
     SDK Version:               2.2.1
     Components Core Version:   1.1.2
     Components CLI Version:    1.4.0

The text was updated successfully, but these errors were encountered:

jconstance-amplify · 2020-01-17T17:54:44Z

@medikoo Any chance this is related to your change?

tylercd100 · 2020-01-17T18:09:11Z

This is happening to me too. I'm getting missing region in config error now and our deployments have been working perfectly for the past year.

Serverless: [AWS apigateway undefined 0.002s 0 retries] getDomainName({ domainName: 'staging.aldermarketing.com' })
 
  Error --------------------------------------------------
 
  Error: Error: Could not set up basepath mapping. Try running sls create_domain first.
  Error: Error: 'staging.aldermarketing.com' could not be found in API Gateway.
  ConfigError: Missing region in config
      at getDomain.then.then.catch (/home/circleci/app/src/node_modules/serverless-domain-manager/index.js:181:15)
      at processTicksAndRejections (internal/process/next_tick.js:81:5)
  From previous event:
      at PluginManager.invoke (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:490:22)
      at getHooks.reduce.then (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:525:24)
  From previous event:
      at PluginManager.run (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:525:8)
      at variables.populateService.then (/usr/local/lib/node_modules/serverless/lib/Serverless.js:133:33)
      at processImmediate (timers.js:637:19)
      at process.topLevelDomainCallback (domain.js:126:23)
  From previous event:
      at Serverless.run (/usr/local/lib/node_modules/serverless/lib/Serverless.js:120:74)
      at serverless.init.then (/usr/local/lib/node_modules/serverless/bin/serverless.js:75:30)
      at /usr/local/lib/node_modules/serverless/node_modules/graceful-fs/graceful-fs.js:136:16
      at /usr/local/lib/node_modules/serverless/node_modules/graceful-fs/graceful-fs.js:57:14
      at FSReqCallback.args [as oncomplete] (fs.js:145:20)
  From previous event:
      at initializeErrorReporter.then (/usr/local/lib/node_modules/serverless/bin/serverless.js:75:8)
      at processImmediate (timers.js:637:19)
      at process.topLevelDomainCallback (domain.js:126:23)
  From previous event:
      at Object.<anonymous> (/usr/local/lib/node_modules/serverless/bin/serverless.js:64:4)
      at Module._compile (internal/modules/cjs/loader.js:738:30)
      at Object.Module._extensions..js (internal/modules/cjs/loader.js:749:10)
      at Module.load (internal/modules/cjs/loader.js:630:32)
      at tryModuleLoad (internal/modules/cjs/loader.js:570:12)
      at Function.Module._load (internal/modules/cjs/loader.js:562:3)
      at Function.Module.runMain (internal/modules/cjs/loader.js:801:12)
      at internal/main/run_main_module.js:21:11

tylercd100 · 2020-01-17T18:14:20Z

Could it be this most recent change? 633a506

medikoo · 2020-01-17T19:12:47Z

This looks as duplicate of #306 which was fixed in #307

Are you relying on latest version of a plugin?

tylercd100 · 2020-01-17T19:15:20Z

I just barely updated to v3.3.1 and it is working for me. @spotnape can you check if the latest version fix your issue?

Thanks @medikoo

jconstance-amplify · 2020-01-17T19:16:44Z

I was also able to verify that it was working with the latest version of the plugin.

brycehemme · 2020-01-19T20:26:37Z

I was experiencing the same issue on serverless-domain-manager version 3.3.0. Bumping to 3.3.1 has fixed the issue for me.

richard-smith-sky · 2020-01-19T20:45:57Z

Thanks all. Bumping the version has resolved our problem too.

shierro · 2020-01-22T08:09:55Z

same here. bumping to 3.3.1 solved issue
OS: MacOS 10.15.2

Framework Core: 1.61.3
Plugin: 3.2.7
SDK: 2.2.1
Components Core: 1.1.2
Components CLI: 1.4.0

gleidsonh · 2020-01-22T10:54:41Z

It works on 3.3.1.
OS: Win10

$ serverless --version
Framework Core: 1.61.3
Plugin: 3.2.7
SDK: 2.3.0
Components Core: 1.1.2
Components CLI: 1.4.0

jconstance-amplify · 2020-01-22T15:20:02Z

Okay, sounds like this is definitely resolved by bumping to 3.3.1. Thanks for confirming folks.

rbjoshi · 2020-01-23T09:23:49Z

I was getting the above error and I updated serverless to 1.61.3 and serverless-domain-manager to 3.3.1 and now I am getting below error while trying to deploy

Serverless Error ---------------------------------------

Serverless plugin "serverless-domain-manager" not found. Make sure it's installed and listed in the "plugins" section of your serverless config file.

Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com

Your Environment Information ---------------------------
Operating System: linux
Node Version: 8.10.0
Framework Version: 1.61.3
Plugin Version: 3.2.7
SDK Version: 2.3.0
Components Core Version: 1.1.2
Components CLI Version: 1.4.0

gleidsonh · 2020-01-23T10:10:02Z

I was getting the above error and I updated serverless to 1.61.3 and serverless-domain-manager to 3.3.1 and now I am getting below error while trying to deploy

Serverless Error ---------------------------------------
Serverless plugin "serverless-domain-manager" not found. Make sure it's installed and listed in the "plugins" section of your serverless config file.
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com
Your Environment Information ---------------------------
Operating System: linux
Node Version: 8.10.0
Framework Version: 1.61.3
Plugin Version: 3.2.7
SDK Version: 2.3.0
Components Core Version: 1.1.2
Components CLI Version: 1.4.0

You must have it on your serverless.yml

plugins:
  - serverless-offline
  - serverless-plugin-include-dependencies
  - serverless-domain-manager

rbjoshi · 2020-01-23T10:26:53Z

I was getting the above error and I updated serverless to 1.61.3 and serverless-domain-manager to 3.3.1 and now I am getting below error while trying to deploy

Serverless Error ---------------------------------------
Serverless plugin "serverless-domain-manager" not found. Make sure it's installed and listed in the "plugins" section of your serverless config file.
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com
Your Environment Information ---------------------------
Operating System: linux
Node Version: 8.10.0
Framework Version: 1.61.3
Plugin Version: 3.2.7
SDK Version: 2.3.0
Components Core Version: 1.1.2
Components CLI Version: 1.4.0

You must have it on your serverless.yml
plugins:
  - serverless-offline
  - serverless-plugin-include-dependencies
  - serverless-domain-manager

@gleidsonh It was there in the serverless.yml but still getting the issue

gleidsonh · 2020-01-23T12:30:05Z

I was getting the above error and I updated serverless to 1.61.3 and serverless-domain-manager to 3.3.1 and now I am getting below error while trying to deploy

You must have it on your serverless.yml
plugins:
  - serverless-offline
  - serverless-plugin-include-dependencies
  - serverless-domain-manager
@gleidsonh It was there in the serverless.yml but still getting the issue

Maybe indentation is incorrect, plugins: must to be glued to the left.

rbjoshi · 2020-01-24T06:00:47Z

I was getting the above error and I updated serverless to 1.61.3 and serverless-domain-manager to 3.3.1 and now I am getting below error while trying to deploy
You must have it on your serverless.yml
plugins:
  - serverless-offline
  - serverless-plugin-include-dependencies
  - serverless-domain-manager
@gleidsonh It was there in the serverless.yml but still getting the issue
Maybe indentation is incorrect, plugins: must to be glued to the left.

@gleidsonh The indentations is as you described, it was working with the older version, but now I am getting the above error

yml snippet

plugins:
  - serverless-plugin-warmup
  - serverless-offline
  - serverless-log-forwarding
  - serverless-domain-manager

custom:
  warmup:
    schedule: 'cron(0/10 12-23 ? * MON-FRI *)'
    prewarm: true
  headers:
    - Content-Type
    - X-Amz-Date
    - Authorization
    - X-Api-Key
    - X-Amz-Security-Token
    - TS-Staging
    - x-tss-correlation-id
    - x-tss-application-id

gleidsonh · 2020-01-24T09:09:12Z

I was getting the above error and I updated serverless to 1.61.3 and serverless-domain-manager to 3.3.1 and now I am getting below error while trying to deploy
You must have it on your serverless.yml
plugins:
  - serverless-offline
  - serverless-plugin-include-dependencies
  - serverless-domain-manager
@gleidsonh It was there in the serverless.yml but still getting the issue
Maybe indentation is incorrect, plugins: must to be glued to the left.
@gleidsonh The indentations is as you described, it was working with the older version, but now I am getting the above error

Is it on package.json, right? Try to remove node_modules and install again. If you are using yarn, clean cache before install.

rbjoshi · 2020-01-24T10:17:15Z

I was getting the above error and I updated serverless to 1.61.3 and serverless-domain-manager to 3.3.1 and now I am getting below error while trying to deploy
You must have it on your serverless.yml
plugins:
  - serverless-offline
  - serverless-plugin-include-dependencies
  - serverless-domain-manager
@gleidsonh It was there in the serverless.yml but still getting the issue
Maybe indentation is incorrect, plugins: must to be glued to the left.
@gleidsonh The indentations is as you described, it was working with the older version, but now I am getting the above error
Is it on package.json, right? Try to remove node_modules and install again. If you are using yarn, clean cache before install.

I removed node_module from the project and package-lock.json and installed the npm from scratch and upgraded the serverless-domain-manager but still getting the issue. I am new to the serverless. Is it compatible with node8.10 ?

gleidsonh · 2020-01-24T12:22:32Z

@rbjoshi Probably AWS no longer allows 8.10, only nodejs10.x and nodejs12.x. Try to update your local npm and serverless.yml. If doesn't works, please submit to a public repository. I'll try to see what's going on.

rbjoshi · 2020-01-25T08:29:23Z

@rbjoshi Probably AWS no longer allows 8.10, only nodejs10.x and nodejs12.x. Try to update your local npm and serverless.yml. If doesn't works, please submit to a public repository. I'll try to see what's going on.

I have created a issue #310 , can you check what am I missing there?

shvhh · 2020-07-28T08:34:14Z

it got fixed when I use

AWS.config.update({
  accessKeyId: process.env.AWS_ACCESS_KEY_ID,
  secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
  region: process.env.AWS_REGION
});

instead of

const config = new AWS.Config({
  accessKeyId: process.env.AWS_ACCESS_KEY_ID,
  secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
  region: process.env.AWS_REGION
})

Vadorequest · 2020-08-25T09:27:48Z

Just encountered the same issue.

Got it fixed by bumping from 3.2.2 to 3.3.2.

himharsh1997 · 2021-01-04T11:14:57Z

AWS_REGION is missing in env.local causing issue on service like s3 getting used in the project.

richard-smith-sky added the bug label Jan 17, 2020

jconstance-amplify closed this as completed Jan 22, 2020

stefanhorning mentioned this issue Jan 24, 2020

Getting 'Unable to fetch information' on create_domain #208

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ConfigError: Missing region in config #308

ConfigError: Missing region in config #308

richard-smith-sky commented Jan 17, 2020 •

edited

Loading

jconstance-amplify commented Jan 17, 2020

tylercd100 commented Jan 17, 2020 •

edited

Loading

tylercd100 commented Jan 17, 2020

medikoo commented Jan 17, 2020

tylercd100 commented Jan 17, 2020

jconstance-amplify commented Jan 17, 2020

brycehemme commented Jan 19, 2020

richard-smith-sky commented Jan 19, 2020

shierro commented Jan 22, 2020

gleidsonh commented Jan 22, 2020

jconstance-amplify commented Jan 22, 2020

rbjoshi commented Jan 23, 2020

gleidsonh commented Jan 23, 2020

rbjoshi commented Jan 23, 2020

gleidsonh commented Jan 23, 2020

rbjoshi commented Jan 24, 2020 •

edited

Loading

gleidsonh commented Jan 24, 2020

rbjoshi commented Jan 24, 2020 •

edited

Loading

gleidsonh commented Jan 24, 2020

rbjoshi commented Jan 25, 2020

shvhh commented Jul 28, 2020

Vadorequest commented Aug 25, 2020

himharsh1997 commented Jan 4, 2021

ConfigError: Missing region in config #308

ConfigError: Missing region in config #308

Comments

richard-smith-sky commented Jan 17, 2020 • edited Loading

Community Note

Bug Report

jconstance-amplify commented Jan 17, 2020

tylercd100 commented Jan 17, 2020 • edited Loading

tylercd100 commented Jan 17, 2020

medikoo commented Jan 17, 2020

tylercd100 commented Jan 17, 2020

jconstance-amplify commented Jan 17, 2020

brycehemme commented Jan 19, 2020

richard-smith-sky commented Jan 19, 2020

shierro commented Jan 22, 2020

gleidsonh commented Jan 22, 2020

jconstance-amplify commented Jan 22, 2020

rbjoshi commented Jan 23, 2020

gleidsonh commented Jan 23, 2020

rbjoshi commented Jan 23, 2020

gleidsonh commented Jan 23, 2020

rbjoshi commented Jan 24, 2020 • edited Loading

gleidsonh commented Jan 24, 2020

rbjoshi commented Jan 24, 2020 • edited Loading

gleidsonh commented Jan 24, 2020

rbjoshi commented Jan 25, 2020

shvhh commented Jul 28, 2020

Vadorequest commented Aug 25, 2020

himharsh1997 commented Jan 4, 2021

richard-smith-sky commented Jan 17, 2020 •

edited

Loading

tylercd100 commented Jan 17, 2020 •

edited

Loading

rbjoshi commented Jan 24, 2020 •

edited

Loading

rbjoshi commented Jan 24, 2020 •

edited

Loading