With platform version 1.4.0, we are unifying these volumes into a single 20GB volume. Fargate tasks now have a consolidated 20GB ephemeral volumeįargate up to platform version 1.3.0 used to have two ephemeral local volumes: a 4GB volume that could be used as a staging ephemeral area for containers running in the same ECS task and a 10GB volume to host container images. FILE SECURE FREE 1.4.0 HOW TOIf you want to know more about how to use this capability please refer to this blog post. AWS Fargate customers can now start running stateful workloads inside Fargate tasks, something that they couldn’t do before.ECS customers using the EC2 launch type no longer need to take care of the heavy lifting of configuring and automating storage on EC2 container instances.Starting today, the ECS task definitions (for both EC2 and Fargate) support the new EFSVolumeConfiguration parameter. AWS Fargate customers did not have the option to deploy stateful workloads because with Fargate there are no EC2 instances that you could access and configure. The automation around making this work was a classic example of undifferentiated heavy lifting. EFS) persistent storage to EC2 container instances and configure tasks to consume that storage. In the true spirit of “customer obsession,” we acted and delivered.įor background, over the years, Amazon ECS customers have implemented custom scripting and solutions to provision zonal (e.g. This feature request had more than 1000 reactions on our open source container roadmap. FILE SECURE FREE 1.4.0 FULLThis enables a full set of new use cases for AWS Fargate. With platform version 1.4.0, we are introducing support for mounting persistent EFS storage inside Fargate tasks. Fargate tasks now support Elastic File System (EFS) endpoints This includes features inherited by the native Fargate platform, some of which are being discussed in this blog. EKS platform versions go above and beyond tracking the Kubernetes versions and include enhancements and additional features support. Note that EKS itself has a notion of platform versions, which is a mechanism that is used in EKS to track the various cluster features and configurations. If you want to read more about the role of Fargate in the container world and specifically its relation to ECS and EKS check out this blog post. Unless otherwise noted, the new features discussed in this blog post are relevant to the native Fargate platform and are directly consumable by the ECS orchestrator. We are going to describe them in this section of the blog post. Platform version 1.4.0 introduces some new AWS Fargate capabilities. What’s new in Fargate platform version 1.4.0? These underlying changes don’t necessarily have a direct relationship with the new customer-visible features but they are just as important. In this blog post, we are going to provide you with a summary of the Fargate features we are enabling with this release and some of the changes we are making underneath. Today we are launching platform version 1.4.0 of AWS Fargate. You can read more about it in the Fargate documentation or you can read the Fargate platform versions primer blog post. The primer blog post goes into more detail about the philosophy behind why we introduced Fargate platform versions and, for example, the practical reasons why we are not tagging platform version 1.4.0 as LATEST just yet. The way the infrastructure features surface to the end users today is through the notion of a Fargate platform version. While Fargate makes the infrastructure disappear in the sense that the customer doesn’t need to think about it, the infrastructure still exists and it’s being managed by AWS. If you want to read more about the role of Fargate in the container world, check out this blog post. While Amazon EC2 abstracts away hypervisors and physical servers from customers, AWS Fargate does the same for container runtimes and EC2 instances. Fargate allows customers to use Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS) to launch applications without the burden of having to deal with the undifferentiated heavy lifting of maintaining, patching, scaling, securing, life-cycling the infrastructure. AWS Fargate is a managed service to run containers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |