amazonka-ecs: Amazon EC2 Container Service SDK.
Amazon EC2 Container Service (Amazon ECS) is a highly scalable, fast, container management service that makes it easy to run, stop, and manage Docker containers on a cluster of Amazon EC2 instances. Amazon ECS lets you launch and stop container-enabled applications with simple API calls, allows you to get the state of your cluster from a centralized service, and gives you access to many familiar Amazon EC2 features like security groups, Amazon EBS volumes, and IAM roles. You can use Amazon ECS to schedule the placement of containers across your cluster based on your resource needs, isolation policies, and availability requirements. Amazon EC2 Container Service eliminates the need for you to operate your own cluster management and configuration management systems or worry about scaling your management infrastructure.
The types from this library are intended to be used with amazonka, which provides mechanisms for specifying AuthN/AuthZ information and sending requests.
Use of lenses is required for constructing and manipulating types. This is due to the amount of nesting of AWS types and transparency regarding de/serialisation into more palatable Haskell values. The provided lenses should be compatible with any of the major lens libraries such as lens or lens-family-core.
[Skip to Readme]
|Versions [faq]||0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 188.8.131.52, 184.108.40.206, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 220.127.116.11, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.5.0, 1.6.0, 1.6.1|
|Dependencies||amazonka-core (==1.3.3.*), base (>=4.7 && <5) [details]|
|Copyright||Copyright (c) 2013-2015 Brendan Hay|
|Maintainer||Brendan Hay <firstname.lastname@example.org>|
|Category||Network, AWS, Cloud, Distributed Computing|
|Source repo||head: git clone git://github.com/brendanhay/amazonka.git|
|Uploaded||by BrendanHay at Fri Oct 9 09:28:25 UTC 2015|
|Downloads||12584 total (827 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
Docs available [build log]
Last success reported on 2015-12-09 [all 4 reports]
For package maintainers and hackage trustees