title: AWS Batch jobs killed due because memory requirement == memory limit?
body: <p>In AWS Batch, when I specify a memory requirement of e.g. 32000MB, my job ends up getting killed because (a) the actual instance autoselected has 64GB memory and (b) ECS seems to view 32000MB as both a requirement <em>and</em> a hard limit (&quot;If your container attempts to exceed the memory specified here, the container is killed&quot; from <a href="https://docs.aws.amazon.com/batch/latest/userguide/job_definition_parameters.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/batch/latest/userguide/job_definition_parameters.html</a>). So as soon as my job goes slightly above 32GB, it gets killed, even though I am happy for it to use up to the 64GB.</p>
  <p>How do I properly specify a minimum memory requirement without causing AWS Batch to kill jobs that go slightly above that? It seems very strange to me that the &quot;memory&quot; parameter appears to be both a minimum and a maximum.</p>
  <p>I assume I'm misunderstanding something.</p>