kubiya_integration
resource allows you to create and manage integrations in the Kubiya platform. Integrations enable connections to external systems like AWS, GitHub, Kubernetes, Jira, and more, allowing agents to interact with these services.
Integrations are the foundation for connecting your agents to external services. They provide secure, configurable connections that can be reused across multiple agents.
Prerequisites
Before using this resource, ensure you have:- A Kubiya account with API access
- An API key (generated from Kubiya dashboard under Admin → Kubiya API Keys)
- Appropriate credentials and permissions for the external systems you want to integrate
Quick Start
Configuration Examples
Configure AWS integration with multiple regions:
Advanced Configurations
Environment-Specific Configurations
Environment-Specific Configurations
Set up environment-specific integration configurations using dynamic blocks:
Jira Integration Setup
Jira Integration Setup
Configure Jira integration for issue tracking:
Arguments Reference
Required Arguments
The name of the integration. Must be unique within your organization.
List of configuration objects. Each config must have:
Name of the configuration.
Whether this is the default configuration. At least one config must be default.
Vendor-specific configuration parameters (varies by integration type).
Optional Arguments
A description of the integration’s purpose and functionality.
Authentication type. Available options:
global
- Global authenticationper_user
- Per-user authentication- Empty string (default)
Type of integration. Available options:
aws
- Amazon Web Servicesaws_organization
- AWS Organizationsgcp
- Google Cloud Platformazure
- Microsoft Azuregithub
- GitHubkubernetes
- Kubernetesjira
- Atlassian Jiraconfluence
- Atlassian Confluence
Vendor-Specific Configuration
Thevendor_specific
map within each config varies by integration type:
Attributes Reference
In addition to all arguments above, the following attributes are exported:The unique identifier of the integration.
Import
Integrations can be imported using their ID:Best Practices
Security
- Use least privilege access for all integrations
- Never hardcode sensitive credentials in configurations
- Regularly audit and rotate access credentials
- Use separate configs for different environments
Configuration
- Always set one configuration as default
- Use clear, descriptive names for integrations
- Document vendor-specific parameters and their purpose
- Group related configurations logically
Testing
- Test integrations in non-production environments first
- Verify connectivity before deploying to production
- Monitor integration health and usage patterns
- Document testing procedures for each integration type
Maintenance
- Keep integration configurations in version control
- Use Terraform modules for common integration patterns
- Implement consistent naming conventions
- Monitor and alert on integration failures
Compatibility
Requirements:
- Kubiya Terraform Provider version >= 1.0.0
- Terraform >= 1.0
- At least one config must have
is_default = true
- Integration names must match exactly when referenced by agents
Important Considerations:
- Some integration types may require additional setup in Kubiya dashboard
- Ensure proper IAM roles and permissions are configured in target systems
- Test connectivity before using integrations in production agents
Troubleshooting
Integration Authentication Issues
Integration Authentication Issues
- Verify IAM roles and permissions in the target system
- Check that ARNs and identifiers are correctly formatted
- Ensure service accounts have necessary permissions
- Test authentication outside of Kubiya first
Configuration Validation Errors
Configuration Validation Errors
- Ensure at least one config has
is_default = true
- Verify all required vendor_specific fields are provided
- Check that integration_type matches available options
- Validate URL formats and endpoints
Agent Integration Access
Agent Integration Access
- Verify integration names match exactly in agent configuration
- Check that the integration is active and properly configured
- Ensure agent has appropriate permissions to use the integration
- Review integration logs for connection issues