There’s supposed to be a sample.zip file but its not there and I’ve tried refreshing the lab several times
Aye, it’s not there. I’ll inform the lab team.
However for now you should be able to complete the lab by creating a file called sample.zip for the lambda to copy. For the purpose of this exercise it should not matter that it’s an empty file, only that a file with that name exists, is copied to the right places and the dynamo log entry appears.
~ on ☁️ (us-east-1) ✖ touch sample.zip
~ on ☁️ (us-east-1) ✖ ls -l
total 4
-rw-r--r-- 1 root root 3285 Mar 6 21:30 lambda-function.py
-rw-r--r-- 1 root root 0 Mar 6 21:37 sample.zip
~ on ☁️ (us-east-1) ➜
Thank you for the help
Now I got this error after creating the zip file
Each time you re-do a task, certain elements of it are randomized, like EC2 instance names, S3 bucket names, files etc.
If the question this time asked for test-file.txt instead of sample.zip and that file was also missing, create it with touch and proceed the question.
Frankly, it is clear that we can try to resolve any strange issues ourselves. However, is this really the way the labs were intended to work?
This is a long lab, it takes time to correctly fill everything - and when you do all that, you are punished by errors (missing file sample.zip that should have been present, error mentioning another file that was not mentioned anywhere before).
I really appreciate what KodeKloud offers with these free labs but maybe a little bit more effort would make them working like expected. (Or just declare in advance that the labs may have errors and that it is part of the game - which I don’t believe is true.)
PS: But maybe a change in approach would help: to do this lab only with the scripts allowing quick repeated gradual troubleshooting.
Frankly, it is clear that we can try to resolve any strange issues ourselves. However, is this really the way the labs were intended to work?
This is a long lab, it takes time to correctly fill everything - and when you do all that, you are punished by errors (missing file sample.zip that should have been present, error mentioning another file that was not mentioned anywhere before).
I really appreciate what KodeKloud offers with these free labs but maybe a little bit more effort would make them working like expected. (Or just declare in advance that the labs may have errors and that it is part of the game - which I don’t believe is true.)
I accept there is an issue with the lab and I did raise a ticket for the lab team at the time (above). There are hundreds and hundreds of labs across this platform and only so many engineers. Fixes get done when the tickets come up in the queue. Bugs that affect multiple labs get priority over ones that affect only one lab. It is the way it is and if you get a job in this field, you will understand.
I provided a workaround so you could clear the lab and progress rather than have to wait for the bug to be fixed.