https://pulumi.com logo
Powered by
a

average-dream-51210

06/25/2019, 3:17 AM
Hrmmm with the Fargate stuff in this post: https://blog.pulumi.com/get-started-with-docker-on-aws-fargate-using-pulumi How do you redeploy code changes of the application image? And do the deploys default to a rolling update of the fargate containers?
w

white-balloon-205

06/25/2019, 3:20 AM
If there are changes in the target app folder, it will re-
docker build
and 
docker push
. The Fargate Service will then be updated to point to this new version of the image, which will trigger a rolling update using the minimum and maximum percentages you can specify.
a

average-dream-51210

06/25/2019, 3:21 AM
*#*$&# freaking awesome!!! 😄
Im assuming with 
const cluster = new awsx.ecs.Cluster("cluster");
I'm able to associate the cluster to a set of public subnets in a VPC so that it can talk to a DB in the private subnets?
If I associate a list of public subnets that reside in different AZs with the cluster, do you know the default deployment strategy of the Fargate tasks in Pulumi? Do they spread across all the AZs?
w

white-balloon-205

06/25/2019, 3:28 AM
Yes - you can pass a 
vpc
parameter to the cluster to associate it with that VPC.
I don’t know the precise spread strategy for Fargate, though I suspect it is documented by AWS.
a

average-dream-51210

06/25/2019, 4:31 AM
awesome thanks!
w

white-balloon-205

06/25/2019, 4:39 AM
FWIW: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html
By default, Fargate tasks are spread across Availability Zones.
Powered by