You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 24, 2020. It is now read-only.
Currently the attack nodes are tagged with the ECS cluster name. This is handy if you search for the nodes, but makes it more difficult for Ops to know at a glance whom the nodes belong to and what their purpose is. It would be useful to also name the ardere attack nodes the way loads-broker does with the --name param.
The text was updated successfully, but these errors were encountered:
Up the socket limits to allow proper outbound connections. Change
tagging call so it's made when running the instances and include
the Name key set to the cluster name for better filtering.
Closes#43, #44
Up the socket limits to allow proper outbound connections. Change
tagging call so it's made when running the instances and include
the Name key set to the cluster name for better filtering.
Closes#43, #44
Currently the attack nodes are tagged with the ECS cluster name. This is handy if you search for the nodes, but makes it more difficult for Ops to know at a glance whom the nodes belong to and what their purpose is. It would be useful to also name the ardere attack nodes the way loads-broker does with the --name param.
The text was updated successfully, but these errors were encountered: