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
    • GitHub
    • 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
    • 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
On this page
  • 1. Add an AWS Target Account
  • 2. Getting to know Fylamynt workflows
  • 3. Creating your first workflow using an AWS Target Account
  • 4. Setting up your first Integration
  • 5. Setting up your first Resource
  • 6. Creating your first Incident Response workflow using Integrations
  • 7. Incident Management Configuration
  • 8. Quickstart - Fylamynt sample workflows

Was this helpful?

  1. Getting started

Onboarding Checklist

Use the provided onboarding checklist to bring yourself up to speed on how everything works and creating powerful workflows in no time at all.

PreviousWelcome to FylamyntNext1. Setting up your first Cloud Service target account

Last updated 3 years ago

Was this helpful?

1.

Adding your AWS target accounts is required to execute AWS API calls as action nodes in a Fylamynt Workflow.

  • The AWS Execution Action allows you to call any AWS API endpoint supported by the .

  • Fylamynt also provides AWS service-specific actions, which are listed .

2.

Fylamynt workflows and the Workflow Editor Canvas are where all the magic happens, providing drag and drop capabilities for all your workflow steps/actions as well as triggering workflows automatically.

3.

AWS API calls are notoriously hard to read, understand and use. Fylamynt provides a step-by-step guide to simplify the process by using the AWS Execution action node to create a workflow.

4.

Integrations are the building blocks of workflows created in Fylamynt. Each Fylamynt integration exposes a set of actions that can be used to create a workflow.

5.

Resources in Fylamynt are either third-party or system plugins that help you with integration setup or provide the necessary elements needed in some of the integration actions.

6.

Fylamynt provides a step-by-step guide to create a workflow that automates the remediation of an alert received from your performance monitoring tool.

Incident Management is the business layer on top of workflow executions and is used to automatically execute the workflow that is associated with a task type assignment.

Sample workflows in Fylamynt can be duplicated to provide users with a quick starting point for their ideal incident response use case.

7.

8.

Add an AWS Target Account
boto3 library
here
Getting to know Fylamynt workflows
Creating your first workflow using an AWS Target Account
Setting up your first Integration
Setting up your first Resource
Creating your first Incident Response workflow using Integrations
Incident Management Configuration
Quickstart - Fylamynt sample workflows