Skip to content

[ECS-Plugin] Document for user #6712

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

Merged
eeshaanSA merged 1 commit into from
Jul 18, 2026
Merged

[ECS-Plugin] Document for user #6712

Show file tree
Hide file tree
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
3 changes: 3 additions & 0 deletions docs/content/en/docs-v1.0.x/plugins/_index.md
View file
Open in desktop
Comment thread
armistcxy marked this conversation as resolved.
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ description: >
| Plugin | Description | Status |
|--------|-------------|--------|
| [Kubernetes multi-cluster](kubernetes-multicluster/) | Deploy a single application to multiple Kubernetes clusters with one pipeline. | Alpha |
| [ECS](ecs/) | Deploy applications to Amazon ECS using the `EXTERNAL` deployment controller | Alpha |

In PipeCD v1, plugins handle deployments. `piped` runs each configured plugin as a separate process and communicates with it over gRPC, so which platforms your `piped` can deploy to depends on which plugins you configure. See more about [plugins](../concepts/#plugins).

There are two types of plugins:
Expand Down Expand Up @@ -52,3 +54,4 @@ To add a plugin to your `piped` and register deploy targets, see [Configuring a
## Writing your own plugin

Anyone can develop a plugin for PipeCD. See the [plugin development guide](../contribution-guidelines/contributing-plugins/) to get started.

Loading
Loading