Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Details needed regarding license and Using Services#7764

ramasva started this conversation inGeneral
Discussion options

Hello Team,

Greetings.

We are using your standalone ec2 based self hosting to test the adaptability for our application. But then we were advised to move in to Self hosted Enterprise Edition.

I need some clarity on that part. Please help.

  1. We are operating on a 100% airgap environment, our application produces 7 - 10 GB logs on a any given day. Here, since the daily ingestion limit for a self hosted Enterprise Edition is 200 GB, we are never going to cross that at any point. As per the organization data policy no data should be shared outside the world. In this case how to handle that license part. I came to know that from your documents that by using traces you can get the ingestion values when needed. Here, we are unfortunately not in a position to share any API / data to you by default. We respect the your ingestion policy so help me on this point.

  2. Instead of s3 for storing the logs can I use EFS service. We are getting some restrictions, please tell me the possibility for the same.

  3. What is the role of RDS here, we knew it stores the meta info regarding the openobserve ( streams, org, function etc info). The question we have here is, Like the self hosted EC2 method, why cant we store the info into the EFS directly instead of using RDS. It's going to be persist anyways. RDS incur lots of cost for us. Please share some light on this.

You must be logged in to vote

Replies: 1 comment

Comment options

@ramasva In regards to your first query I can confirm that if you are self-hosting in your env, you have complete control over your data- so it is not shared with anyone including O2 org unless you choose to do that.

EFS can act similarly to local disk storage for OpenObserve in Local mode/Single Node, as it can be mounted as a data directory on the EC2 instance and used to store both stream data and SQLite metadata. For Cluster mode, replacing S3 with EFS is not possible as object storage is a hard requirement here. Considering your daily ingestion volume single node should be fine for your use case , although I am not sure about the performance with EFS under heavy I/O.

RDS (PostgreSQL) is used in O2's Cluster mode to store metadata because it provides reliability, concurrency, and high availability for production workloads. In Local mode, metadata is stored in SQLite on disk, which can be placed on EFS by mounting it as the data directory, making EFS a viable option for single-node testing to avoid RDS costs.

@hengfeiyang Feel free to add/correct anything here. Thx!

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
None yet
2 participants
@ramasva@Manazsharma
Converted from issue

This discussion was converted from issue #7758 on July 30, 2025 09:02.


[8]ページ先頭

©2009-2025 Movatter.jp