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

Was this helpful?

  1. Getting started

5. Setting up your first resource

Previous4. Setting up your first IntegrationNext6. Creating your first Incident Response workflow

Last updated 3 years ago

Was this helpful?

Now that you have seen the process of enabling integrations in Fylamynt, it's time to understand how resources are used in the product.

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.

For example:

  • API Keys are unique to your organization and are used for authorization of webhook-type integrations with Fylamynt. For many integrations, an API key is required, so it is recommended that you first create this resource before configuring your integrations.

  • Github Repos are needed for getting project files/templates used in Terraform or Pulumi actions.

  • S3 Buckets are needed to read pre-existing data stored in an S3 bucket for a given step in a workflow or for capturing, re-using or persisting output data from a given step in a workflow.

Each resource has a different purpose to serve in Fylamynt. Resources are created to support the infrastructure that in the end is required to create a workflow.

To configure a resource in Fylamynt:

  • Click on "Settings" in the left panel of the product

  • You should by default be in the Integration tab

  • Scroll down to see the list of available Resources

  • Select a Resource that you would like to configure

  • Fill out the parameters presented on the screen

  • Click Save