<p>ConfigMaps in Kubernetes are <a href="https://kubernetes.io/docs/concepts/configuration/configmap/#:%7E:text=The%20data%20stored%20in%20a,separate%20database%20or%20file%20service." rel="nofollow noreferrer">limited to 1Mib</a>. If your file could not be split or shrunk, I feel you should use a volume to store it using the storage class that your cloud vendor/subsystem offers you.</p>
<p>S3 is a good object store, but you can't store ConfigMaps in it.
You can't use it either to store volumes. You could use EBS and EFS (since we are talking about AWS products) based on access pattern that you want to achieve for this filesystem.</p>

CC BY-SA 4.0
2022-04-13T20:22:51.953Z
can we use EBS or EFS for config Map?
amit singh
CC BY-SA 4.0
2022-05-02T20:55:17.190Z
Nope, ConfigMap is a specific object that is stored in the KeyValue distributed datastore (es. Etcd) and so far we are not allowed to change where this object is stored.
Alberto P.
CC BY-SA 4.0
2022-04-13T13:40:22.070Z
2022-04-13T17:58:11.127Z
2022-04-13T17:58:11.127Z
Alberto P.
<p>I have a ConfigMap which stores Nginx configs and It is getting <code>size exceeded</code>. There are many site configs in there so I can't create multiple ConfigMaps.</p>
<p>I thought of using S3 to store ConfigMap, is it an option? If it is, how can one achieve it.</p>

<kubernetes><amazon-s3>
Use S3 To Store ConfigMap
amit singh
# Use S3 To Store ConfigMap

(Asked by: username_0 on 2022-04-12)

I have a ConfigMap which stores Nginx configs and It is getting `size exceeded`. There are many site configs in there so I can't create multiple ConfigMaps.

I thought of using S3 to store ConfigMap, is it an option? If it is, how can one achieve it.

**Tags:** kubernetes, amazon-s3


---

## 1 answers

### Answer by username_1 on 2022-04-13. Score: 3 | Accepted answer

ConfigMaps in Kubernetes are [limited to 1Mib](https://kubernetes.io/docs/concepts/configuration/configmap/#:%7E:text=The%20data%20stored%20in%20a,separate%20database%20or%20file%20service.). If your file could not be split or shrunk, I feel you should use a volume to store it using the storage class that your cloud vendor/subsystem offers you.

S3 is a good object store, but you can't store ConfigMaps in it.
You can't use it either to store volumes. You could use EBS and EFS (since we are talking about AWS products) based on access pattern that you want to achieve for this filesystem.

> **Comments:**
> **username_0**: can we use EBS or EFS for config Map?  
> **username_1**: Nope, ConfigMap is a specific object that is stored in the KeyValue distributed datastore (es. Etcd) and so far we are not allowed to change where this object is stored.  

---

