5 ms·

Is there any plan for Fargate + EKS to be able to support attached EBS volumes? Please say yes.

bbgm 9y ago
We are super interested in enabling EBS support for Fargate. We do not have any timelines, but would love to know what your expectations are and what you would use EBS for. (I run the containers org at AWS)
- lotyrin 9y ago
  Goal is to have a developer write up a service definition with e.g. a web tier, service tier and database tier, wherein some of those pods might need to have persistent data volumes and expect EKS be able to run that application for them without my intervention, even if I were to have something shooting the underlying compute nodes in the head (but ideally, I won't even sweat those nodes' existence thanks to Fargate). We'd be using services like RDS for everything we could, of course, but sometimes someone insists on persisting something to disk, and sometimes that strategy makes sense.
- elcritch 9y ago
  One good example use case would be running distributed NoSQL / KV stores. Running say a Riak KV cluster or an image caching and processing service. Both of these would probably be best using SSD EBS's to be able to bring the data storage and computing closer together rather than using RDS or similar, which in certain use cases it can be significantly faster due to less network calls and latency. As an example setup, Rancher has a plugin to allow using docker data volumes from EBS volumes. It handles the naming, attaching the drives to the EC2 instance, etc.
- nathankunicki 9y ago
  I currently run Cassandra inside a container. The data is on an EBS volume, attached to the instance through CloudFormation at stack creation time, and mounted through a systemd unit defined in UserData (Also through CloudFormation). It is then exposed to the container via a Docker volume mapping specified in the task definition (Also through CloudFormation!). Would love to have an extension of the run-task command that specifies an EBS volume to attach and where to mount it when using Fargate.
- Rapzid 9y ago
  Pet sets describing EBS requirements. This way if a pet set instance is migrated the volume can be moved and set up with it.
- politician 9y ago
  One of our use-cases involves operating a time-series database for collecting app metrics, InfluxDB.
- rad_gruchalski 9y ago
  Silly question! Of course we should be able to attach EBS. How else does one provide data persistence. Please don't say "efs".
nhumrich 9y ago
yes edit: (I dont actually know, im just saying yes cause you asked)
- bbgm 9y ago
  :) and if you ever have questions or feedback we are a tweet away.
  - shroom 9y ago
    Is there any work in progress to simplify AWS console. With so much (more) cool stuff being announced AWS feels a bit overwheling for some, me included. I’m refering to the UI part mostly and some concepts like policys and user mangement. Forgive if this is the wrong place to ask... then Ill try Twitter ;-)
deleted 9y ago
[deleted]

bbgm 9y ago

We are super interested in enabling EBS support for Fargate. We do not have any timelines, but would love to know what your expectations are and what you would use EBS for. (I run the containers org at AWS)

lotyrin 9y ago
Goal is to have a developer write up a service definition with e.g. a web tier, service tier and database tier, wherein some of those pods might need to have persistent data volumes and expect EKS be able to run that application for them without my intervention, even if I were to have something shooting the underlying compute nodes in the head (but ideally, I won't even sweat those nodes' existence thanks to Fargate). We'd be using services like RDS for everything we could, of course, but sometimes someone insists on persisting something to disk, and sometimes that strategy makes sense.
elcritch 9y ago
One good example use case would be running distributed NoSQL / KV stores. Running say a Riak KV cluster or an image caching and processing service. Both of these would probably be best using SSD EBS's to be able to bring the data storage and computing closer together rather than using RDS or similar, which in certain use cases it can be significantly faster due to less network calls and latency. As an example setup, Rancher has a plugin to allow using docker data volumes from EBS volumes. It handles the naming, attaching the drives to the EC2 instance, etc.
nathankunicki 9y ago
I currently run Cassandra inside a container. The data is on an EBS volume, attached to the instance through CloudFormation at stack creation time, and mounted through a systemd unit defined in UserData (Also through CloudFormation). It is then exposed to the container via a Docker volume mapping specified in the task definition (Also through CloudFormation!). Would love to have an extension of the run-task command that specifies an EBS volume to attach and where to mount it when using Fargate.
Rapzid 9y ago
Pet sets describing EBS requirements. This way if a pet set instance is migrated the volume can be moved and set up with it.
politician 9y ago
One of our use-cases involves operating a time-series database for collecting app metrics, InfluxDB.
rad_gruchalski 9y ago
Silly question! Of course we should be able to attach EBS. How else does one provide data persistence. Please don't say "efs".

nhumrich 9y ago

yes edit: (I dont actually know, im just saying yes cause you asked)

bbgm 9y ago
:) and if you ever have questions or feedback we are a tweet away.
- shroom 9y ago
  Is there any work in progress to simplify AWS console. With so much (more) cool stuff being announced AWS feels a bit overwheling for some, me included. I’m refering to the UI part mostly and some concepts like policys and user mangement. Forgive if this is the wrong place to ask... then Ill try Twitter ;-)

deleted 9y ago

[deleted]