More configurable options for ECS agent #2480
Unanswered
mbaciu-gpsw
asked this question in
Q&A
Replies: 1 comment
-
Hi, currently there isn't a way to configure those features in Bottlerocket's API system. I created an issue to track the implementation of them: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
searching through docs, discussions, PRs and code, looks like bottlerocket exposes only a subset of the available configuration options for the ecs agent (eg
logging-drivers
,allow-privileged-containers
,loglevel
,enable-spot-instance-draining
andimage-pull-behavior
). While all these are quite useful for us , there are still some configs for which we have a use case, and not all of them have an alternative (like eg addresing them at the task definition level).Here are some of these ecs agent configs that we're missing right now in bottlerocket:
ECS_TASK_METADATA_RPS_LIMIT
: we've been bumping this (as advised by AWS support), after noticing 429s returned by the ecs agent when hitting the /v2/credentials endpointECS_CONTAINER_STOP_TIMEOUT
: we've used this with some containers that took a little more time to terminate that the default 30 seconds. Helped with services ending up unnecessarily redoing jobs that were probably very close to finish.ECS_ENGINE_TASK_CLEANUP_WAIT_DURATION
: helped us with the host volume being filled with data used by stopped tasks.ECS_RESERVED_MEMORY
: unless I'm wrong, this is set to the default 0 in bottlerocket. AWS documentation suggest to also reserve some memory for the Amazon ECS container agent. We've also been using it.My questions: is configuring above supported with the ecs variant? And if not, is this something that could be considered for a new feature?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions