Use the Container integration for running a script that’s packaged in a container to remediate an incident.
In today's world, we often come across scripts (e.g. Bash, Python scripts) and code in Containers that is being used in remediating problems in the infrastructure. With this integration we support executing these scripts in our workflows and help users connect these scripts to other services available in Fylamynt.
Note that the container images used in this action node need to be set up according to https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/
Additionally, the target account role needs to have its Trust Relationships updated to allow access to the AWS lambda service, and an updated Condition clause as shown.
The Container integration lets you:
- Configure a container registry.
- Pick a Docker image and version that’s available in the registry.
- Pass any input to the Docker image in a text box. The input is directly passed as input when running the container.
- Enter resource requirements for the container
- CPU (specified in CPU units).
- MEM (specified in MB)
- Drag the Container Action node onto the workflow editor canvas
- Select Alias for the target account in the dropdown
- Select Repository from the dropdown
- Select Image from the dropdown
Target account alias for running the container
Container repository in the alias target account
Container image SHA256 in the selected repository
S3 bucket for log output from container run
extra command arguments
Image entry point
Memory size for container run, default is 128 MBytes
Timeout in seconds for the run, default is 900 seconds
Working directory for the run
S3 bucket in which log files are stored (if specified in inputs)
S3 key of log file (if a bucket was specified)
output from the run
Last 4 KB of the execution log of the run