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.
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