How are you deploying to production? Did you mean that you are running the meteor tool in production (with the bundled node version)?
We do not run “meteor” nor the “bundled node version” in production. But our custom AMI uses the meteor team’s forked node version. Some folks might be ok with the provided AMI by AWS
We use mup and the EB plugin.
mup will use nvm to install the version of node required by meteor - so the version bundled with the AMI isn’t important.
AFAIR the problem with deploying Meteor 2.15 on a Node 20 machine in EBS was related to Python and the compilation of/by pre-gyp/node-gyp which I think is used/necessary by bcrypt.
Updates about the first Meteor 3.0 RC Release:
Due to some roadblocks, our ETA for the RC Release has been postponed to 19th April.
These are the tasks for the first RC:
meteor update --release 3.0-beta.7You can follow the updates on What’s left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.
It is time for a Weekly update 
We are proud to say that we have the first Release Candidate for Meteor 3.0 
You can check more details about it here.
The priority of the next RC will be to review and fix issues with Cordova’s experience.
You can follow the updates on What’s left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.
It is time for a Weekly update
We are proud to say that we have the Release for 2.16 beta
You can check more details about it here .
Tasks and fixes for the next Meteor 3.0 RC:
waitUntilAllLoaded safety check. by radekmie · Pull Request #13102You can follow the updates on What’s left until an official Meteor 3.0? Discussion, and on the Release 3.0 PR.
Can this be included in the next RC candidate?
Yes, it will be included in RC.2!
It is time for a Weekly update
We are proud to say that we have the Release for Meteor 3.0-rc.1
You can check more details about it here.
We also have the Meteor 2.16-rc.0
You can check more details about it here.
Tasks and fixes for the next 3.0 RC:
It is time for a Weekly update
We are proud to say that we have the Release for Meteor 2.16 official
You can check more details about it here.
It’s time for a weekly update
It’s been some time, but we are proud to say that we have the Release for Meteor 3.0-rc.2
You can check here for more details.
Tasks and fixes for the next, and final until the official, Meteor 3.0 Release Candidate (rc.3):
Meteor 3-rc.3 is expected to arrive on Tuesday, June 11th, stay tuned.
These dates are subject to change as we add or remove things from the backlog.
Congrats to Meteor. Finally it’s coming
Can someone confirm this “warning” in the migration document?
TIP
It is not recommended to use concurrent calls. Use
awaitfor yourMeteor.callAsync.
Previously, this was only the case if you have stubs. It seems that the “stubs qualifier” is no longer applicable based on the current migration document
You can still use Meteor.call if you know what you’re doing (not using it with stubs as you mentioned). We recommend that you use Meteor.callAsync because you won’t need to think about stubs when calling a method, and it will prevent weird behavior.
@denyhs, I am referring to Meteor.callAsync() in this case. The migration document I linked above mentioned not to use it concurrently.
Then there is this example:
// it is not recommended to use concurrent calls
Promise.all([ // This is not ok
Meteor.callAsync('someMethod'),
Meteor.callAsync('someMethod')
]).then(([data1, data2]) => {
console.log(data1, data2);
});
Yeah, I will review everything in this part of the document. It’s now confusing and seems outdated.
It’s time for a weekly update
We are proud to say that we have the Release for Meteor 3.0-rc.4
You can check here for more details.
Tasks and fixes for the next, and official, Meteor 3.0 Release:
addEmailAsync aliasMeteor 3.0 is expected to arrive on Tuesday, July 8th, stay tuned.
These dates are subject to change as we add or remove things from the backlog.
I really like the proactive communication form that’s taking place from the Meteor team, showing current and future plans along with past achievements. Please keep them coming 
Weekly Update June 28th, 2024
So far we have released rc4 as we mentioned in our previous updates, and work is progressing well for our official Meteor 3 release.
You can check here for more details about our last Release Candidate.
The backlog has evolved a little over the last days with some issues gaining priority, our most important ones are as follows:
meteor-tool is missing, this has gone up in priority but it’s extremely hard to solve, we have a path forward but have some loose ends we need to account for, some tests on Windows are failing at the moment@vlasky/whomst since it depends on a package called posix which builds a binary and breaks on some installationsWe also confirmed that Cordova is working completely fine, this was done by @nachocodoner, one of our developers with the most expertise in that area.
We are also revamping the documentation and researching ways to simplify the mechanics for call and callAsync, we have @denyhs at this forefront and also huge help from @zodern . The goal is to make Meteor have the best Developer Experience as possible and the migration as simple as possible too.
Other tasks and fixes for the next, and official, Meteor 3.0 Release:
addEmailAsync aliasasyncLocalStorage globaltinytest major version increaseMeteor 3.0 is expected to arrive on Monday, July 8th or 15th at the most
Next Releases
These dates are subject to change as we add or remove things from the backlog.
This new ECMA 2024 constructor might help in this particular case. Promises for asynchronous programming [ES6]