# **eb deploy**

## Description

Deploys the application source bundle from the initialized project directory to the running application.
If git is installed, EB CLI uses the `git archive` command to create a `.zip` file from the contents of the most recent `git commit` command.
However, when `.ebignore` is present in your project directory, the EB CLI doesn't use git commands and semantics to create your source bundle. This means that EB CLI ignores files specified in `.ebignore`, and includes all other files. In particular, it includes uncommitted source files.
**Note** 
You can configure the EB CLI to deploy an artifact from your build process instead of creating a ZIP file of your project folder. See [Deploying an artifact instead of the project folder](eb-cli3-configuration.md#eb-cli3-artifact) for details.
## Syntax

 **eb deploy** 
 **eb deploy {{environment-name}}** 
## Options

**** 
| Name | Description | 
| --- | --- | 
&#124; `-l` {{version\_label}}<br />or<br />`--label` {{version\_label}} &#124; Specify a label to use for the version that the EB CLI creates. If the label has already been used, the EB CLI redeploys the previous version with that label.<br />Type: String &#124; 
&#124; --env-group-suffix {{groupname}} &#124; Group name to append to the environment name. Only for use with [Compose Environments](ebcli-compose.md). &#124; 
&#124; `-m` "{{version\_description}}"<br />or<br />`--message` "{{version\_description}}" &#124; The description for the application version, enclosed in double quotation marks.<br />Type: String &#124; 
&#124; `--modules` {{component-a component-b}} &#124; List of components to update. Only for use with [Compose Environments](ebcli-compose.md). &#124; 
&#124; `-p`<br />or<br />`--process` &#124; Preprocess and validate the environment manifest and configuration files in the source bundle. Validating configuration files can identify issues prior to deploying the application version to an environment. &#124; 
&#124; `--source codecommit/{{repository-name}}/{{branch-name}}` &#124; CodeCommit repository and branch. &#124; 
&#124; `--staged` &#124; Deploy files staged in the git index instead of the HEAD commit. &#124; 
&#124; `--timeout` {{minutes}} &#124; The number of minutes before the command times out. &#124; 
&#124; `--version` {{version\_label}} &#124; An existing application version to deploy.<br />Type: String &#124; 
&#124; [Common options](eb3-cmd-options.md) &#124; &#124; 
## Output

If successful, the command returns the status of the `deploy` operation.
If you enabled CodeBuild support in your application, **eb deploy** displays information from CodeBuild as your code is built. For information about CodeBuild support in Elastic Beanstalk, see [Using the EB CLI with AWS CodeBuild](eb-cli-codebuild.md).
## Example

The following example deploys the current application.
```
$ eb deploy
2018年07月11日 21:05:22 INFO: Environment update is starting.
2018年07月11日 21:05:27 INFO: Deploying new version to instance(s).
2018年07月11日 21:05:53 INFO: New application version was deployed to running EC2 instances.
2018年07月11日 21:05:53 INFO: Environment update completed successfully.
```</div><div class="naked_ctrl">
<form action="/index.cgi/contrast" method="get" name="gate">
<p><a href="http://altstyle.alfasado.net">AltStyle</a> によって変換されたページ <a href="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb3-deploy.md">(-&gt;オリジナル)</a>
/ <label>アドレス: <input type="text" name="naked_post_url" value="https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb3-deploy.md" size="22" /></label> <label>モード: <select name="naked_post_mode">
<option value="default">デフォルト</option>
<option value="speech">音声ブラウザ</option>
<option value="ruby">ルビ付き</option>
<option value="contrast" selected="selected">配色反転</option>
<option value="larger-text">文字拡大</option>
<option value="mobile">モバイル</option>
</select>
<input type="submit" value="表示" />
</p>
</form>
</div>