Skip to main content
Visitor II
May 10, 2021
Question

I am trying to deploy dsh-predmnt to my personal aws account but serverless is throwing a lot of errors. I followed the PDF document "How to deploy DSH-PREDMNT in proprietary AWS account" . Is there a more detailed instruction on deploying to AWS??

  • May 10, 2021
  • 2 replies
  • 2673 views

PS C:\pm\predictive_maintenance_fe\serverless>node --version

v14.16.1

PS C:\pm\predictive_maintenance_fe\serverless>npm --version

7.11.1

PS C:\pm\predictive_maintenance_fe\serverless>npm install

   up to date, audited 190 packages in 2s

   6 packages are looking for funding

   run `npm fund` for details

   found 0 vulnerabilities

PS C:\pm\predictive_maintenance_fe\serverless>

PS C:\pm\predictive_maintenance_fe\serverless> serverless deploy --verbose

Serverless: Deprecation warning: Serverless Framework was enhanced with a new variables resolver which doesn't recognize "provider.variableSyntax" setting.Starting with a new major it will be the only resolver that's used.. Drop setting from a configuration to adapt to it

   More Info: https://www.serverless.com/framework/docs/deprecations/#NEW_VARIABLES_RESOLVER

[dataLakeZipBuilder] lambda configured with buckets: pmsensors-weeklylake and pmsensors-ziplake

[zipFileRemover] lambda configured with bucket: pmsensors-ziplake

Serverless: Deprecation warning: CLI options definitions were upgraded with "type" property (which could be one of "string", "boolean", "multiple"). Below listed plugins do not predefine type for introduced options:

    - AdditionalStacksPlugin for "skip-additionalstacks", "stack"

    - Remover for "verbose"

    - Assets for "verbose", "bucket"

   Please report this issue in plugin issue tracker.

   Starting with next major release, this will be communicated with a thrown error.

   More Info: https://www.serverless.com/framework/docs/deprecations/#CLI_OPTIONS_SCHEMA

Serverless: Deprecation warning: Unresolved variable references will be communicated with a thrown error, starting from next major

   More Info: https://www.serverless.com/framework/docs/deprecations/#VARIABLES_ERROR_ON_UNRESOLVED

 Serverless Warning --------------------------------------

 A valid file to satisfy the declaration 'file(./output.json):CDNDistributionId' could not be found.

Serverless: Configuration warning at 'functions.customResourceLambda': unrecognized property 'DependsOn'

Serverless:

Serverless: Learn more about configuration validation here: http://slss.io/configuration-validation

Serverless:

Serverless: Deprecation warning: Starting with next major, Serverless will throw on configuration errors by default. Adapt to this behavior now by adding "configValidationMode: error" to service configuration

   More Info: https://www.serverless.com/framework/docs/deprecations/#CONFIG_VALIDATION_MODE_DEFAULT

Serverless: Deprecation warning: Support for "package.include" and "package.exclude" will be removed with next major release. Please use "package.patterns" instead

   More Info: https://www.serverless.com/framework/docs/deprecations/#NEW_PACKAGE_PATTERNS

Serverless: Packaging service...

Serverless: WARNING: Function dataLakeZipBuilder has timeout of 900 seconds, however, it's attached to API Gateway so it's automatically limited to 30 seconds.

Serverless: Deploying additional stacks...

Serverless: Writing template for additional stack eventsQueueNestedStack...

Serverless: Creating additional stack eventsQueueNestedStack...

...

Serverless: Additional stack eventsQueueNestedStack created successfully (CREATE_COMPLETE).

Serverless: Writing template for additional stack zipBuilderNestedStack...

Serverless: Creating additional stack zipBuilderNestedStack...

......

Serverless: Additional stack zipBuilderNestedStack create failed (ROLLBACK_COMPLETE).

 Error ---------------------------------------------------

 Error: Additional stack zipBuilderNestedStack create failed (ROLLBACK_COMPLETE)

  at C:\pm\predictive_maintenance_fe\serverless\node_modules\serverless-plugin-additional-stacks\index.js:480:37

  at processTicksAndRejections (internal/process/task_queues.js:93:5)

  at async PluginManager.invoke (C:\Users\chakradhar\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:552:9)

  at async PluginManager.run (C:\Users\chakradhar\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:598:7)

  at async Serverless.run (C:\Users\chakradhar\AppData\Roaming\npm\node_modules\serverless\lib\Serverless.js:313:5)

  at async C:\Users\chakradhar\AppData\Roaming\npm\node_modules\serverless\scripts\serverless.js:634:9

  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

    This topic has been closed for replies.

    2 replies

    ST Employee
    May 13, 2021

    Hi @VChak.1​ ,

    the issue could lie in compatibility o versions used for the deploy

    Can you try to use serverless --version Framework Core: 1.70.1 Plugin: 3.6.11 SDK: 2.3.0 Components: 2.30.10 and run it again?

    hope this helps

    Niccolò

    VChak.1Author
    Visitor II
    May 13, 2021

    I tried your suggestion but still the deploy is failing ...

    C:\predictive_maintenance_fe\serverless>serverless --version

    Framework Core: 1.70.1

    Plugin: 3.8.4

    SDK: 2.3.2

    Components: 2.34.9

    C:\predictive_maintenance_fe\serverless>node --version

    v12.22.1

    C:\predictive_maintenance_fe\serverless>npm --version

    7.11.1

    C:\predictive_maintenance_fe\serverless> serverless deploy --verbose

    Serverless: Deploying additional stacks...

    Serverless: Writing template for additional stack eventsQueueNestedStack...

    Serverless: Creating additional stack eventsQueueNestedStack...

    Serverless: Additional stack eventsQueueNestedStack created successfully (CREATE_COMPLETE).

    Serverless: Creating additional stack zipBuilderNestedStack...

    Serverless: WARNING: Inappropriate call of provider.request()

    Serverless: [AWS cloudformation 200 0.19s 0 retries] describeStacks({ StackName: 'predictive-maintenance-dev-zipBuilderNestedStack' })

    Serverless: Additional stack zipBuilderNestedStack create failed (ROLLBACK_COMPLETE).

     Error --------------------------------------------------

     Error: Additional stack zipBuilderNestedStack create failed (ROLLBACK_COMPLETE)

       at C:\predictive_maintenance_fe\serverless\node_modules\serverless-plugin-additional-stacks\index.js:480:37

     From previous event:

       at processImmediate (internal/timers.js:461:21)

     From previous event:

       at readMore (C:\predictive_maintenance_fe\serverless\node_modules\serverless-plugin-additional-stacks\index.js:462:10)

     Your Environment Information ---------------------------

       Operating System:     win32

       Node Version:       12.22.1

       Framework Version:     1.70.1

       Plugin Version:      3.8.4

       SDK Version:        2.3.2

       Components Version:    2.34.9

    C:\predictive_maintenance_fe\serverless>

    On the CloudFormation Stack Error Event In AWS Console ...

    Logical ID:

    predictive-maintenance-dev-zipBuilderNestedStack

    ERROR EVENT:

    The following resource(s) failed to create: [zipFileRemoverRole, zipBuilderRole, roleForDataLakeWeeklyAggregatorLambda, weeklyAggregationLake, zipTable, weeklyAggregationBucketPolicy, dataLake, zipLake]. Rollback requested by user.

    The IAM User used for serverless is an Administrator With Full Access and the Additional stack eventsQueueNestedStack is created successfully.

    But create "predictive-maintenance-dev-zipBuilderNestedStack" is FAILING .

    Please help.

    ST Employee
    May 14, 2021

    Hi @VChak.1​ ,

    maybe you need to manually delete anything that was created before the error

    then you can retry to run serverless and let me know if it works this way

    Niccolò

    Visitor II
    July 8, 2021

    I am also trying to deploy it to my personal aws account amd facing this issue that you mentioned here why the service is looking very ordinary in this task?