Repository navigation
Replies: 3 comments 3 replies
|
The S3 bucket name is presumed to be |
|
I have implement the feature allowing the user to define their own S3 bucket instead of creating a new on feature and would like to create a PR for it. But since this is my first time contributing to a project, eventhough i already read your contributor guideline, it's still quite confusing on how to be able to create PR, can you allow me to become a contributor of artillery? Super happy to contribute to such an amazing project :DD |
|
Same there, worked at 3 major compagnies , all had strict restriction in resource name , and not only for s3 , role names , etc Also for secrets lot’s are using secret manager instead of ssm |
Uh oh!
There was an error while loading. Please reload this page.
Title: Reusing existing S3 / SQS / supporting resources with
run-fargateHi all — networking is sorted on my side; this is purely about the supporting AWS resources
run-fargateprovisions (S3, SQS, CloudWatch Logs, IAM).From the docs I understand the per-run lifecycle:
artilleryio-log-group, 180-day retention (configurable viaARTILLERY_LOGGROUP_RETENTION_DAYS)artilleryio-ecs-worker-rolereused if it already existsWhat I'd like to confirm for a governed account where resource creation is restricted:
S3 — Can I point Artillery at an existing, pre-provisioned bucket (specific name / KMS encryption / bucket policy) instead of it creating/managing its own? Is the bucket name configurable, and what are the minimum bucket permissions the CLI and workers need?
SQS — Is the per-run queue creation/teardown mandatory, or can an existing queue be supplied? For accounts where
sqs:CreateQueue/DeleteQueueis locked down, what's the recommended approach? Any constraints (FIFO vs standard, encryption, naming prefixartilleryio*)?CloudWatch Logs — Can the log group name be customized (not just retention)? Can I pre-create the group and have Artillery write to it rather than create it?
Pre-provisioning everything in Terraform — Is there a documented/canonical set of resources + ARNs so a platform team can create them up front (bucket, log group, role/policy) and grant the CLI only
Get/Userather thanCreatepermissions? Essentially: what's the least-privilege, "bring your own resources" setup forrun-fargate?Goal is to run with no
Create*permissions on S3/SQS/Logs — only reuse. If that isn't currently supported, knowing the hard requirements (e.g. SQS must be per-run) would help me scope the IAM policy correctly.Thanks!
All reactions