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
  • Configure CloudFormation in Fylamynt
  • Integration Actions
  • CloudFormation Run Template

Was this helpful?

  1. RESOURCES

CloudFormation Templates

PreviousAPI KeysNextCloudWatch Targets

Last updated 3 years ago

Was this helpful?

Configure CloudFormation in Fylamynt

  • Navigate to Settings > Resources > CloudFormation

  • Click Manage Resource to create and configure a new integration instance

  • Click on Add New

Details needed to set up CloudFormation instance in Fylamynt:

Parameters

Description

Required

Template Id

Unique human readable name for resource

True

Repo Id

Github repo id

True

Ref

Github commit ref, (ie: main/master)

False

File Path

Absolute filepath of template file

True

Note:

Here Repo Id is a drop down and values populate from the Git Resources, please click to learn more about Git resources

Follow the steps listed below to get the desired parameters to enter in Fylamynt

  • Template Id parameter is the unique human readable name for resource, any string could be provided, Since this is unique identifier 2 resources can not have the same template id

  • Login to your Github Account

  • Open your Repository

  • In above picture after username attribute is Repo Id (ie: <username>/<repoId>), copy the repo id

  • Here parameter Ref is any branch or any commit, (Note: If not provided default branch would be used)

  • Here File Path parameter is the absolute path of template json file (with respect to root of the Repo), In below image as can be seen the aws_ec2.json is the template file, hence file path would be mydir/aws_ec2.json

Integration Actions

You can add these actions in Fylamynt workflow builder, as part of your workflow.

CloudFormation Run Template

Integration node to run CloudFormation Run Template

Input

Parameter Name

Description

Required

Select Alias

AWS assume role alias

True

Select Template

Template Id of configured cloudformation resource

True

Parameters

Parameters for your CF template

False

Note: Make parameters dynamic for user, a template JSON file may or may not contain the parameters, but if template file does not contain the parameters then this should be provided at runtime or run would fail

Output

Parameter Name

Type

Description

execution_status

String

Status of run (ie: S_OK / E_FAIL)

stack_id

String

Newly created ID of stack

Action Example

CloudFormation Run Template
here