This is a Nullstone application module that provides the same workflow as other container apps in Nullstone. However, because it is only a task, it does not create infrastructure for a long-running service. Instead, the task is executed manually using the outputs from this module.
ECS Task is a great choice for applications that require 2 things:
- Running jobs triggered on a schedule, from a queue, or manually
- Running on your own ECS cluster backed by EC2 instances that you manage
Security scanning is graciously provided by Bridgecrew. Bridgecrew is the leading fully hosted, cloud-native solution providing continuous Terraform security and compliance.
When a task is triggered by events or through the CLI, it is placed into private subnets on the connected network. As a result, the ECS Task can route to services on the private network.
Since it is a task, no ports are exposed privately or publicly. It does not provide support for attaching load balancers, API Gateways, etc.
This application module supports various capabilities to handle execution of an ECS Task.
- Trigger: Enable events to execute ECS Task (e.g. Cron Trigger, SQS Queue)
- CLI Execution:
nullstone exec(Seeexecfor more information)
Logs are automatically emitted to AWS Cloudwatch Log Group: /<task-name>.
To access through the Nullstone CLI, use nullstone logs CLI command. (See logs for more information)
Nullstone automatically injects secrets into your ECS Task through environment variables. (They are stored in AWS Secrets Manager and injected by AWS during launch.)