Fylamynt Product Docs
Search…
Fylamynt Product Docs
Welcome to Fylamynt
Getting started
Onboarding Checklist
1. Setting up your first Cloud Service target account
2. Getting to know workflows
3. Creating your first workflow using AWS Cloud Services
4. Setting up your first Integration
5. Setting up your first resource
6. Creating your first Incident Response workflow
7. Incident Management - Automatic workflow execution
8. Quickstart - Fylamynt sample workflows
Integrations
Amazon EventBridge
Ansible
AWS
AWS Health
Container
Datadog
Elasticsearch
Generic Webhook
Google Kubernetes Engine (GKE)
Humio
Instana
Jenkins
Jira
New Relic
Opsgenie
PagerDuty
Pulumi
Prometheus
ServiceNow
Slack
Splunk
Splunk On-Call (VictorOps)
Spot by Netapp
Squadcast
Sumo Logic
Teleport
Terraform Cloud
Terraform CLI
Twilio
Zoom
AWS Services
EC2
Service Health
RESOURCES
API Keys
CloudFormation Templates
CloudWatch Targets
EKS Permissions
Github Repos
S3 Buckets
SSH Targets
FEATURED WORKFLOWS
Stop or Terminate underutilized AWS resources
Rightsizing EC2 instances
Incident Response Automation
Application Performance Monitoring
Announcement
What's new?
Support
Contact Fylamynt
Powered By GitBook
Container
Use the Container integration for running a script that’s packaged in a container to remediate an incident.

Overview

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.

Use Cases

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)

Integration Actions

  • 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
Input
Parameter Name
Description
Required
alias
Target account alias for running the container
True
repository
Container repository in the alias target account
True
image
Container image SHA256 in the selected repository
True
bucket
S3 bucket for log output from container run
False
command
extra command arguments
False
entry_point
Image entry point
False
memory_size
Memory size for container run, default is 128 MBytes
False
timeout
Timeout in seconds for the run, default is 900 seconds
False
working_directory
Working directory for the run
False
Output
Parameter Name
Type
Description
bucket
String
S3 bucket in which log files are stored (if specified in inputs)
key
String
S3 key of log file (if a bucket was specified)
output
String
output from the run
log
String
Last 4 KB of the execution log of the run
Integrations - Previous
AWS Health
Next - Integrations
Datadog
Last modified 10mo ago
Copy link
On this page
Overview
Use Cases
Integration Actions