Is artillery-plugin-aws-sigv4 being maintained any longer?

[RJKeane2000]

Although there a bot updates and recommended code changes for bugs, there hasn't been any activity to pull in these changes and release a new version since 0.0.5 (Sept 17th, 2020). If this plugin is no longer maintained, is there an alternative to this plugin? It's a really useful plugin so I'm hoping we can get a few more contributors added to keep it going.

[gabor386]

Hi @RJKeane2000 , did you find any alternative ?

[RJKeane2000]

Hi @gabor386. I have not. I have a really hacky way of getting it to work though. I downloaded Richard Seig's fix and added the file to my test directory. Then before I execute the test, I overlay the aws-sigv4.js file that comes with the latest version of artillery-plugin-aws-sigv4 with the fixed version. So my package.json scripts command looks like this:

{
   "scripts": {
      "performance-test": "cp ./aws-sigv4.js ./node_modules/artillery-plugin-aws-sigv4/lib & npx artillery run performance-test.yml -o performance-results.json"
    }
}

I'm just kicking the can down the road though. I love how easy it is to set up a performance test with Artillery but long term I have to move away from this plugin. I've been watching the main artillery.io project to see if new features would make this plugin obsolete.

[gabor386]

@RJKeane2000 Thank you for your response. Did you face with this error message before ? #41

[RJKeane2000]

I'm not seeing that error. I'm running on Node 18 alpine, with the 2.0.0-27 of artillery. Something that may help you figure out what's happening is this:

export DEBUG=http,http:capture,http:response

Good luck!

[marti-jorda-roca]

Hi this happens if we do not define any header in the artillery yaml. I've created a PR that corrects this .

But you can set a dummy header and for me it worked.

[Ishvarya]

Hello,
Is the plugin in usable state?
I get this error-

WARNING: Could not load plugin: aws-sigv4 warn
WARNING: Plugin aws-sigv4 specified but module artillery-plugin-aws-sigv4 could not be found (MODULE_NOT_FOUND) warn

installing the npm package globally did not help..