Open sujin-sam opened 7 months ago
Sorry for the late reply. I'm taking a look
Extension is not working for me as well and logs are showing nothing. I was playing with different values and trying to check code of the extension. It's not working with provided.al2 for 100%.
Just wanted to confirm the issue with the arn:aws:lambda:eu-central-1:871265522301:layer:chaos-lambda-extension-x86_64-unknown-linux-gnu-release:9
layer as well. I'm trying to integrate it into the Chaos Toolkit AWS extension. The latency fault works not the other one.
Sorry for the late reply. I'm taking a look
@having-fun-serverless any luck ?
I just stumbled upon the same issue while testing and found this closed issue here:
And after changing my env var to CHAOS_EXTENSION__RESPONSE__ENABLE_CHANGE_REPONSE_BODY
with the missing S in RESPONSE
it worked.
Seems like this fix isn't in version 9 yet...
I'm using a lambda function with the below configs arch: x86_64 runtime: python3.10
I tested the chaos extension in us-east-1 and us-east-2, the Latency attack is working fine, but the Response Body Change is not working
US-East1 ARN: arn:aws:lambda:us-east-1:871265522301:layer:chaos-lambda-extension-x86_64-unknown-linux-gnu-release:12 US-East2 ARN: arn:aws:lambda:us-east-2:871265522301:layer:chaos-lambda-extension-x86_64-unknown-linux-gnu-release:11
Enabled DEBUG logs, did not see any errors. Unfortunately, I cannot be able to upload the logs, as those are in my organization's function.
The below env variables were added for the attacks:
Latency Attack
Response Change Attack