AWS Lambda

[bertbeck]

I'd like to use this code in an AWS Lambda. Is it possible to get a unique 16 bit id for the lambda instance it is running in? The equivalent of AmazonEC2MachineID() but for Lambdas.

As I understand it - Lambda's are limited to 1000 instances - so if we could get something like a "slot" number, ir a unique number from 0 to 999, 1 to 1000 etc - that would be even better and we could reduce the size of the server id field.

@yuokada (or anyone) please let me know if this is possible. I would pay for help with this.

[yuokada]

I'm just a contributor. I have no responsibility for this repo.

TO: the owner of this repo. Please consider to put the CODEOWNER file or something to reveal the owner.

[bertbeck]

did you write the AWS code?

…

On Thu, Nov 10, 2022 at 8:55 PM Yukihiro Okada (Yuki) < ***@***.***> wrote: I'm just a contributor. I have no responsibility for this repo. TO: the owner of this repo. Please consider to put the CODEOWNER file or something to reveal the owner. — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABO7WQUL54Q7XKV4LZ7TG5DWHWRQ7ANCNFSM6AAAAAAR4TCRTM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[yuokada]

Unfortunately, I've never written the code using this library on AWS lambda.

But, as far as I roughly read your comment, it doesn't sound good to shrink random IDs to less than 1000.
In my understanding, each lambda instance (or container) is unique and not reusable. So, we should give an unique ID (or number) to it.

[bertbeck]

thanks - maybe a lambda is not the best day to do this - maybe using an ec2 nano is a better way

…

On Fri, Nov 11, 2022 at 12:03 AM Yukihiro Okada (Yuki) < ***@***.***> wrote: Unfortunately, I've never written the code using this library on AWS lambda. But, as far as I roughly read your comment, it doesn't sound good to shrink random IDs to less than 1000. In my understanding, each lambda instance (or container) is unique and not reusable. So, we should give an unique ID (or number) to it. — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABO7WQXVDHMQ6KG43HXSJSLWHXHQ7ANCNFSM6AAAAAAR4TCRTM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[YoshiyukiMineo]

The continuity of server instances is important because Sonyflake is based on system clocks. So in that sense, AWS Lambda is not suitable to run Sonyflake.