AWS Fargate, a new product that lets you use containers as a fundamental compute primitive without having to manage the underlying instances, is now available for use with Amazon ECS, according to an announcement from AWS.
Here are some of the key features of AWS Fargate that might be of interest.
Flexible configuration options
There are 50 different combinations of CPU and memory within Fargate, so you can find a close match for exactly what you need for your specific applications and your workload requirements.
Fargate runs its tasks within your own VPC, while also supporting awsvpc networking mode and the elastic network interface. This allows you to separate responsibility so you retain full control of the networking policies for your applications. Fargate also supports the use of public IP addresses.
Load balancing support
The tool also supports ECS Service Load Balancing for the Application Load Balancer and Network Load Balancer. You can specify the IP addresses of each Fargate task to register with the load balancers.
While there aren’t any instances to manage with Fargate, you can use it to group tasks into logical clusters. You can manage who can run or view services within the cluster in Fargate. There’s also a new Task Execution Role that lets you use Amazon ECS permissions to perform various operations like pushing logs to CloudWatch Logs or pulling images from Amazon Elastic Container Registry.
Container registry support
Using the Task Execution Role, you can easily authenticate items to help with tasks like pulling images from Amazon ECR. Or if you’re using a public repository like DockerHub, this feature lets you continue making use of those tools.
AWS Fargate: Pricing and billing
Wondering how much Fargate will cost your organization? There isn’t one set price. Instead, you pay by the task size, only paying for the time for which resources are consumed by the task. The price is charged on a per-second basis, with a one-minute minimum charge included as well.
Photo credit: Pixabay