Skip to content

Add deploy command and more instruction for deploying a new service #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
khashf wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add deploy command and more instruction for deploying a new service #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,14 @@ After the CloudFormation templates have been deployed, the [stack outputs](http:

### How to Deploy

Stack is setup to launch stack in the us-west-2 (Oregon) region in your account:
Stack is setup to launch stack in the us-west-2 (Oregon) region in your account.

Launch the `master.yaml` from aws cli with command:
```
aws cloudformation create-stack --stack-name <your stack name> --template-body file://<absolute path to the local master.yaml> --capabilities CAPABILITY_NAMED_IAM --parameters ParameterKey=KeyPairName,ParameterValue=<Name of your AWS account's key pair>
Copy link
Collaborator

@MikeTheCanuck MikeTheCanuck Apr 27, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do we do to update CF with a new version of the master.yaml for an existing stack? Do we just substitute update-stack parameter for the create-stack parameter here?


```


### Customize the templates

Expand All @@ -68,9 +75,9 @@ Stack is setup to launch stack in the us-west-2 (Oregon) region in your account:

1. Push your container to a registry somewhere (e.g., [Docker Hub](https://hub.docker.com/), [Amazon ECR](https://aws.amazon.com/ecr/)).
2. Copy one of the existing service templates in [services/*](/services).
3. Update the `ContainerName` and `Image` parameters to point to your container image instead of the example container.
3. Update the `ContainerName` and `Image` parameters to point to your container image instead of the example container. Also make sure the `ContainerName` of property `LoadBalancers` of the ECS service matches with the `Name` in `ContainerDefinitions` property of `TaskDefinition`.
Copy link
Collaborator

@MikeTheCanuck MikeTheCanuck Apr 27, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it also necessary to change the Image value (at least the final suffix) found under service.yaml > Resources > TaskDefinition > Properties > ContainerDefinitions ?

4. Increment the `ListenerRule` priority number (no two services can have the same priority number - this is used to order the ALB path based routing rules).
5. Copy one of the existing service definitions in [master.yaml](master.yaml) and point it at your new service template. Specify the HTTP `Path` at which you want the service exposed.
5. Copy one of the existing service definitions in [master.yaml](master.yaml) and point it at your new service template. Specify the HTTP `Path` at which you want the service exposed. Upload the `service.yaml` file of your new service to S3 and update its link in `master.yaml`
6. Deploy the templates as a new stack, or as an update to an existing stack.

### Setup centralized container logging
Expand Down