Monitoring Jump Starts: Node.js 10 update

Michael Wittig – 13 Nov 2019

AWS recently announced that we are not able to create Lambda functions running on Node.js 8 after January 6, 2020. Monitoring Jump Starts connect you with all relevant AWS sources for comprehensive monitoring coverage. Some of our Jump Starts rely on Lambda functions. Therefore, we updated the Jump Starts to use Node.js 10 instead.

Update required

The following Jump Starts require an update:

Monitoring goal CloudFormation Template URL
AWS basics https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot.yml
EC2 instance https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-ec2-instance.yml
EC2 instances https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-ec2-instances.yml
Elastic Beanstalk https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-elastic-beanstalk.yml
ElastiCache memcached cluster https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-elasticache-memcached.yml
CloudFormation Drift Detection https://s3-eu-west-1.amazonaws.com/monitoring-jump-start/marbot-cloudformation-drift.yml

Update procedure

To update a Jump Start:

  1. Visit the AWS Management Console.
  2. Double-check the selected AWS region.
  3. Search for marbot.
    Update: step 1
  4. Select a stack and grab the matching CloudFormation Template URL from the table above (the Description has to match the Monitoring goal here!).
  5. Click on Update.
  6. Select Replace current template and paste the CloudFormation Template URL into the Amazon S3 URL field.
    Update: step 2
  7. Click on Next.
  8. Scroll to the bottom of the page and click on Next.
  9. Once again, scroll to the bottom of the page and click on Next.
  10. Scroll to the bottom of the page and select I acknowledge that AWS CloudFormation might create IAM resources.
    Update: step 3
  11. Click on Update stack.
  12. Repeat this procedure for every CloudFormation stack that is based on the updated Jump Starts.
  13. If you use more than one AWS region, repeat the procedure for each region.

Summary

AWS Lambda ends support for Node.js 8. To prepare for the future (January 6, 2020), you have to update our Monitoring Jump Starts as described in this post.

Further help is available here:

Michael Wittig

Michael Wittig

I’m the author of Amazon Web Services in Action. I work as a software engineer, and independent consultant focused on AWS and DevOps.

You can contact me via Email, Twitter, and LinkedIn.

Briefcase icon
Hire me
marbot teaser

Incident Management for Slack

Team up to solve incidents with marbot. Never miss a critical alert. Escalate alerts from your AWS infrastructure among your team members. Strong integrations with all parts of your AWS infrastructure: CloudWatch, Elastic Beanstalk, RDS, EC2, ...

Slack icon
Try for free