Contents

---
title: ufo deploy
---

It is useful to sometimes deploy only the task definition without re-building it.  Say for example, you are debugging the task definition and just want to directly edit the `.ufo/output/hi-web.json` definition. You can accomplish this with the `ufo deploy` command.  The `ufo deploy` command will deploy the task definition in `.ufo/output` unmodified.  Example:

```
ufo deploy hi-web
```

The above command does the following:

1. register the `.ufo/output/hi-web.json` task definition to ECS untouched.
2. deploys it to ECS by updating the service

The `ufo deploy` command does less than the `ufo ship` command.  Typically, people use [ufo ship]({% link _docs/ufo-ship.md %}) over the `ufo deploy` command do everything in one step:

1. build the Docker image
2. register the ECS task definition
3. update the ECS service

The `ufo ships`, `ufo ship`, `ufo deploy` command support the same options. The options are presented here again for convenience:

{% include ufo-ship-options.md %}


<a id="prev" class="btn btn-basic" href="{% link _docs/ufo-ships.md %}">Back</a>
<a id="next" class="btn btn-primary" href="{% link _docs/ufo-scale.md %}">Next Step</a>
<p class="keyboard-tip">Pro tip: Use the <- and -> arrow keys to move back and forward.</p>

Version data entries

5 entries across 5 versions & 1 rubygems

Version	Path
ufo-3.1.2	docs/_docs/ufo-deploy.md
ufo-3.1.1	docs/_docs/ufo-deploy.md
ufo-3.1.0	docs/_docs/ufo-deploy.md
ufo-3.0.1	docs/_docs/ufo-deploy.md
ufo-3.0.0	docs/_docs/ufo-deploy.md