maxmustermann/pulumi
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add a note about IAM, credentials, region, etc. flowing from AWS IaaS to CaaS

Browse source
This commit is contained in:
joeduffy 2016-11-04 13:10:50 -07:00
parent 25e0979da3
commit 2226584cff
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/targets.md
View file

@ -264,8 +264,10 @@ Targeting the [ECS](http://docs.aws.amazon.com/AmazonECS/latest/developerguide/)
service manage scheduling of containers on EC2 VMs. It is only legal when using the AWS IaaS provider.
First and foremost, every Cluster containing at least one `mu/container` in its transitive closure of Stacks gets an
associated [ECS cluster](http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_GetStarted.html). A reasonable
default number of instances, of a predefined type, are chosen, but you may override them (TODO(joe): how).
associated [ECS cluster](http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_GetStarted.html).
A reasonable default number of instances, of a predefined type, are chosen, but you may override them (TODO(joe): how).
All of the AWS-wide settings, such as IAM, credentials, and region, are inherited from the base AWS IaaS configuration.
The next difference is that, rather than provisioning entire VMs per `mu/container`, each one maps to an [ECS service](
http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html).