@hashicorp
The AWS ECS plugin deploys an application image to an AWS ECS cluster. It also launches on-demand runners to do operations remotely.
- Official
- Built-in
Updated last year
- GitHub(opens in new tab)
AWS ECS Platform
Archive Notice
This integration relates to a legacy version of Waypoint and is no longer actively maintained.Parameters
57 Results
Provides additional configuration for using an ALB with ECS
the ARN on an existing ALB to configure when this is set, Waypoint will use this ALB instead of creating its own. A target group will still be created for each deployment, and will be added to a listener on the configured ALB port (Waypoint will the listener if it doesn't exist). This allows users to configure their ALB outside Waypoint but still have Waypoint hook the application to that ALB
how many cpu shares the container running the application is allowed on Fargate, possible values for this are configured by the amount of memory the container is using. Here is a complete listing of possible values: 512MB: 256 1024MB: 256, 512 2048MB: 256, 512, 1024 3072MB: 512, 1024 4096MB: 512, 1024 5120MB: 1024 6144MB: 1024 7168MB: 1024 8192MB: 1024
Health check settings for the app.
Provides additional configuration for logging flags for ECS Part of the ecs task definition. These configuration flags help control how the awslogs log driver is configured.
Security Group IDs of existing security groups to use for the ECS service's network access list of existing group IDs to use for the ECS service's network access. If none are specified, waypoint will create one. If DisableALB is false (the default), waypoint will only allow ingress from the ALB's security group
Additional container to run as a sidecar. This runs additional containers in addition to the main container that comes from the build phase.