title: How to provide a config file to a Fargate Task?
body: <p>What is the easiest way to provide one or several external configuration file(s) to an app running as an AWS Fargate task?</p>
  <ul>
  <li>The files cannot be part of the Docker image because they depend on the stage environment and may contain secrets.</li>
  <li>Creating an EFS volume just for this seems to be overengineered (we only need read access to some kb of properties).</li>
  <li>Using the AWS SDK to access a S3 bucket at startup means that the app has a dependency to the SDK, and one has to manage S3 buckets.*</li>
  <li>Using AWS AppConfig would still require the app to use the AWS SDK to access the config values.*</li>
  <li>Having hundreds of key-value pairs in the Parameter Store would be ugly.</li>
  </ul>
  <p>*It is an important aspect of our applications to not depend on the AWS SDK, because we need to be able to deploy to different cloud platforms, so solutions that avoid this are preferable.</p>
  <p>It would be nice to just be able to define this in the task definition, so that Fargate mounts a couple of files in the container. Is this or a similar low-key solution available?</p>