WordPress Application #23 in "Done"

[deniseddi]

Requirement:

• service type replica

Should it be explicit in the code?

In the docs, under resource “aws_ecs_service”, there is an argument reference:
*scheduling_strategy (https://www.terraform.io/docs/providers/aws/r/ecs_service.html#scheduling_strategy) - (Optional) The scheduling strategy to use for the service. The valid values are REPLICA and DAEMON. Defaults to REPLICA.

The Replica scheduling strategy places and maintains the desired number of tasks across your cluster.
The Daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. When using this strategy, there is no need to specify a desired number of tasks

Requirement:

• deployment type rolling update or blue/green* (first is easier, second is better)

Using Blue-Green Deployment to Reduce Downtime and Risk | Cloud Foundry Docs

Deployment Strategies Defined | Itay as a Service *

• at least 2 task definitions running at any point in time

[drii-cavalcanti]

Requirement:

• service type replica

Should it be explicit in the code?

I'll add the line scheduling_strategy = "REPLICA" in the aws_ecs_service resource, just in case.

Requirement:

• deployment type rolling update or blue/green* (first is easier, second is better)

Using Blue-Green Deployment to Reduce Downtime and Risk | Cloud Foundry Docs

Deployment Strategies Defined | Itay as a Service *

• at least 2 task definitions running at any point in time

We've got 2 TD running for each container.

[deniseddi]

Hey Adriana,
The service already defaults to REPLICA. I guess we only add the code if we decide to go with Daemon

[drii-cavalcanti]

Hey Adriana,
The service already defaults to REPLICA. I guess we only add the code if we decide to go with Daemon

Yeap! I was gonna add into the code, just in case. Do you think it is necessary still?