Alternative to public subnets

[adavies48]

Hey I was wondering if there is a work around to using public subnets? In my company they're restricted and not possible to implement. I've seen in the docs and from a response to a chat that public subnets are required, but there must be a way to use artillery without them? Any help would be great thanks.

[bernardobridge]

Hi @adavies48 👋,

You can create your own VPC with private subnets and have Artillery run in it by using the --subnet-ids flag (you can also configure security groups similarly).

Here's the reference for the CLI flags:
https://www.artillery.io/docs/reference/cli/run-fargate#fargate-specific-flags

[adavies48]

Great thank you, I will try that.

[bernardobridge]

Apologies @adavies48 , this information is actually incorrect. Please refer to the post below for the correct details:

#2437 (comment)

[hassy]

You have to run in a public subnet to be able to pull Docker images from Artillery's public ECR repository.

The workaround is to:

• clone Artillery's worker image and host it in your own private ECR repo
• edit the IAM role that Artillery generates to allow pulls from your private ECR repo
• configure Artillery to use your own copy of the worker image by setting the WORKER_IMAGE_URL environment variable to the URL of the image in your private ECR repo

We'll support this natively in Artillery at some point but no ETA on that right now.

[drdj85]

@Mathdon @hassy I had the same problem after doing this the exact same way with the -p and had to sideline this. Any way forward would be great if you can help?

[hassy]

@Mathdon @drdj85 How are you keeping your own copy of the image up to date? The entrypoint did indeed change recently (in b9d895b#diff-a33800f8944e9e0680e8427bdbe98ef51764c448e6681c5a68737ca2c304fc19L35). That change will be released in Artillery v2.0.12 which will also set the new entrypoint automatically. So you can either:

1. Upgrade to v2.0.12 when it's out on Monday May 13
2. Rebuild your private image using the Dockerfile from v2.0.11 (or earlier if you're on an earlier version of Artillery)

[drdj85]

@hassy manually pulling and pushing to private ecr. Thanks for the information, I’ll get the new image and give it another go when it’s released. Thanks for the help.

[Mathdon]

HI @hassy I have updated the image and updated to artillery 2.0.12 and have received a different error

runc create failed: unable to start container process: exec: "/artillery/loadgen-worker": stat /artillery/loadgen-worker: no such file or directory

Any ideas on this?

[Mathdon]

Hi @hassy

Any idea of how we can resolve this?