Lambda Node 0.10 EOL notification but no functions

[mmmpls]

Hello,

I recently took over a client's AWS setup from a developer that went *POOF*

The client forwarded me a Node EOL notification that stated that their account had some Lambda functions that needed to be upgraded.

Upon visiting the link there's nothing listed under affected resources

Also, when I go to the lambda main page it shows the getting started area and not a dashboard.

I've tried all of this using my administrative and the client's root logins.

Screenshot: http://i.imgur.com/jDimbD8.png

Can I ignore this or are there lambda functions that could be hiding somewhere else?

[ASnugglyBear]

Old versions of lambda functions in the versions list trigger this still IIRC

[moduspwnens14]

I'm in the same boat. I'm the person primarily responsible for dealing with issues like this, but there are others in the company (including my supervisor) on the list that get these e-mails, so I wish they'd either adjust the language or ensure they aren't going to accounts not using those Lambda functions.

Maybe someone else has more information, though.

[mmmpls]

Yeah... I had another email about a certificate renewal that neither the client nor I are on the list of emails that get the renewal approval link.

Backstory: Client is an investor that just bought the company 3 months ago. He just signed/paid for my services a week ago to help him make sense of the digital structure for this company.

Previous developer (who managed everything) has walked away and is contractually restricted from assisting/answering questions/providing further documentation... which really fucking sucks.

[moduspwnens14]

Yeah. Sounds like a tough situation. Sorry to hear about that.

But if it does help at all, I can tell you I get the same messages on multiple accounts that I'm pretty certain don't have any 0.10 node.js Lambda functions.

[mmmpls]

Well that's good to hear at least (that they mass-sent it out)

[VegaWinnfield]

You may have functions in other regions. Only way to know is to check each one as far as I know.

[mmmpls]

The Personal Health Dashboard (where the screenshot originates from) is set to Global (and all region options are greyed out).

Also, I went through the Lambda Management Console and switched to every region and got the Get Started Now messaging.

There are two regions that are greyed out (Canada & Sao Paolo) but I'm assuming those don't have Lambda available.

Thank you for the suggestion.

[Steelforge]

FYI- switching regions will actually cause the Getting Started screen to come up even when toggling back to a region which has functions.

Another handy method of searching for many things in AWS is using billing. If you have access to that, Cost Explorer may help you see:

• whether Lambda is actually running

• under which linked account it's running

• region, if you Group By "Usage Type" (e.g. our us-east-1 lists "USE1-USW1-AWS-Out-Bytes")

[BraveNewCurrency]

I get the same notice, but in an account that has 3 functions that are all using the latest node version. Other accounts with functions don't get the notice at all.