A container that you can use to provide config files from s3 into another container deployed with this. Useful for deploying images from vendors you don't want to extend, but need to provide conf files for. https://hub.docker.com/repository/docker/tarfeef101/s3_sidecar

tarfeef101 112b253e88 fix misnamed basename flag in script 3 tahun lalu
Dockerfile 0e093d8660 added basename option 3 tahun lalu
README.md 0e093d8660 added basename option 3 tahun lalu
docker-compose.yaml 0e093d8660 added basename option 3 tahun lalu
entrypoint.sh 112b253e88 fix misnamed basename flag in script 3 tahun lalu

README.md

aws_s3_sidecar

Purpose

Run this container as a sidecar to other services in a deployment environment like an ECS cluster/service/task, K8S cluster/pod, etc. The container can be used to pull config files from S3 and expose them so that your other containers can access them through a shared volume without relying on persistent storage. This is useful for situations where you may be deploying someone else's images (like a vendor) and don't want to extend them and deal with hosting your own repos, etc. but you need to bring in configuration files or something similar to get them working.

Usage

Deploy the container in an environment where it inherits an IAM role (i.e. an ECS task role), or provide the environment variables necessary to get aws-cli to pick up the credentials. To specify what files to expose, set the following environment variables:

  • BUCKET should be the bucket you wish to retrieve the files from
  • FILES is a |-delimited list of files within the bucket you wish to be exposed. Their full key will be used unless you use the BASENAME flag.
  • BASENAME should be set to 1 if you want the files to be renamed to be only the basename (so /opt/basename vs /opt/full/key/path/basename).

The files will be exposed in a volume in /opt, which you should then mount in to any other containers you wish to acccess the files.