> For the complete documentation index, see [llms.txt](https://resmocom.gitbook.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resmocom.gitbook.io/product/getting-started/glossary.md).

# Glossary

### Account & User

A user and an account are automatically created after signup. 

Learn more about accounts: [Accounts](/product/settings/accounts.md)

Learn more about users: [User](/product/users-and-permissions/user.md)

### Integration

Integration is used to feed the required data for Resmo to do its job. They are easy to integrate and secure by default.

Learn more about integrations: [Integrations Guide](/product/integrations/integrations-guide.md)

### Resource

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:

```json
{ 
    accountId:"935339171232" 
    amiId:"ami-372gd78g23rc1" 
    availabilityZone:"eu-central-1a" 
    instanceId:"i-1b9f37t81aec3a631" 
    instanceType:"t2.nano" 
    name:"application-server" 
    networkInterfaces:[] 
    publicIp:null 
    region:"eu-central-1" 
    state:"running" 
    subnetId:"subnet-2310d721" 
    tags:{}
}
```

Each resource has an associated key and configuration data:

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

Learn more about resources: [Resources](/product/resources/resources.md)

### Query

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.

Learn more about queries: [Queries](/product/queries/query-types.md) 

### Resource Group

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
* accounts
* teams

Learn more about resource groups: [Tag Rules](/product/resource-tags/resource-groups.md)

### Rule

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.

Learn more about rules: [Rules](/product/rules/rules.md)

### Pack

Packs are used to group rules. They offer ready-to-use templates for common best practices and compliance frameworks.

Learn more about conformance packs: [Packs (Compliance and Security Best Practices)](/product/packs/packs.md)

### Notification

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.

Learn more about notification: [Notification Channels](/product/notifications/notification-channels.md) 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://resmocom.gitbook.io/product/getting-started/glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.