Service : AWS Lambda, Function nautilus-priorities-queue-function has Memory 128 MB and Timeout 423 seconds. Allowed Memory: 256 MB and Allowed Timeout: 10 seconds. Service : AWS Lambda, Function xfusion-priorities-queue-function has Memory 128 MB and Timeout 425 seconds. Allowed Memory: 256 MB and Allowed Timeout: 10 seconds.
As you can see from the limits set for the Lambda service in AWS Playgrounds. Due to security concerns, the max timeout you can set is 10 seconds, but you have set 423 seconds.
Hi Santosh,
I worked on that lambda service in 100 Days of Cloud (AWS)
Day 46: Event-Driven Processing with Amazon S3 and Lambda on 2026-07-28
but now i am not able to open aws playground.
You may have noticed the note in the description of the Day 46 question, which specifically mentions setting the timeout and memory limits. The Playgrounds also display the same warning.
It’s possible that the system detected the activity as misuse and blocked the account.
may I Know how to unblock my account?
Could you please share what were you trying with and why the timeout was set to more than the defined allowed limit of 30 seconds?
I am not sure about allowed limit of 30 seconds during the Day 46 question task, which specifically mentions setting the timeout and memory limits. but aftet some time i redo the task and completed the Day 46 question task. now when i open AWS Playgrounds i got this error.
Hi Prakash
Just wanted to check, any specific reason the limits were amped up to
423 seconds.
Hi @TanishkaMarrott,
There is no specific reason for 423 seconds on that task, i wrongly provide the value. But now I am not able to open any playground.
Hi @Alistair_KodeKloud,
yes, I thought it would be some network issue from my side. then only I came to know about that my account has been locked. now they unlock my account. Thanks for asking.
So you are all good now?
The question does now state lambda settings. In July it did not.
