# Cache Services

Stackmate offers infrastructure deployment for major managed cache services (like AWS Elasticache for example)

### What you get when introducing this service to your configuration

* A managed cache instance with sane defaults

### Required attributes

* `type` - **string** - It should be either `redis` or `memcached`

### Optional attributes

* `size` - **string** - The instance size. Should be one of the instances the provider has available
* `version` - **string** - The cache version to use. These are dictated by the cloud provider (eg. AWS) and it's one of the versions they currently support.
* `storage` - **number** - The size of the storage space in Gigabytes
* `port` - **number** - The port to use. By default, `6379` is assigned to `redis` and `11211` is assigned to `memcached`
* `monitoring` - **object** - Any monitoring options available for the service. Example configuration is shown below

The typical [Common Service Options](https://docs.stackmate.io/configuration-file/environments#common-service-options) apply here too.

### Example configuration

```yaml
# ... the rest of the configuration ...
environments:
  production:
    # ... more services ...
    my-cache:
      type: redis
      provider: aws         # optional when your provider's set to aws
      region: eu-central-1  # optional if you have a region set for the project
      size: cache.t3.micro
      storage: 30
      version: 7.0
      monitoring:
        urls:
          - https://a-webhook-to-get-alerted-by.com
        emails:
          - cache-alerts@mywebsite.com
```


---

# Agent Instructions: 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:

```
GET https://docs.stackmate.io/configuration/cache-services.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.