A glossary of key concepts and terminology used throughout Resmo
A user and an account are automatically created after signup.
Integration is used to feed the required data for Resmo to do its job. They are easy to integrate and secure by default.
Resources are entities created, updated or deleted in integration tools.
Asset and resource keywords are used interchangeably. Resmo collects a resource's configuration, not the data itself.
For example, an Amazon EC2 instance has a resource like this in Resmo:
Each resource has an associated key and configuration data:
- ie. GitHub has repositories or users which you can access using github_repository and github_user keys in Resmo.
- Configuration data - in JSON format
- See the EC2 example above.
Users can query resources using SQL. Our SQL interface is powerful and easy to get started. Resmo offers ready-to-use queries for all integrations. Users can also write their own queries, save and share them with others.
Resource groups are used to organize Resmo resources. They are used to view, filter, manage resources easily.
Common use-cases for resource groups:
- development, staging and production environments
Rules represent desired states for resources. They are used to evaluate resource's configuration data against specified settings. Resmo offers managed rules (predefined) and custom rules (customizable). Rule notifications can notify users as soon as a violation happen.
ie. Ensure IAM password policy prevents password reuse.
Packs are used to group rules. They offer ready-to-use templates for common best practices and compliance frameworks.
Notifications are used to notify users. Resmo supports many notification channels like e-mail, webhook, Slack, Opsgenie and more. Customers can receive real-time or regular updates via notifications.