Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifications on external_port usage and storing session recordings in S3 #1184

Closed
vjmax opened this issue Dec 20, 2024 · 3 comments
Closed

Comments

@vjmax
Copy link

vjmax commented Dec 20, 2024

external_port: What is the purpose of the external_port parameter in the Warpgate configuration file? when would it need to be modified?

Session Recordings in S3: Is it possible to store Warpgate session recordings in an Amazon S3 bucket?
Is there a built-in feature in Warpgate to directly upload session recordings to S3?

@Eugeny
Copy link
Member

Eugeny commented Dec 20, 2024

external_port is used to construct connection URLs and settings that are shown to users on the UI - you'll need it if you map Warpgate ports to different port numbers on the NAT

Session recordings can only be stored on the filesystem

@Eugeny Eugeny closed this as completed Dec 20, 2024
@vjmax
Copy link
Author

vjmax commented Jan 1, 2025

When Using Warpgate for long periods consumes significant disk space due to session recordings. While recordings are currently stored on the filesystem, disk space becomes a concern for long-term usage.

Question:
Is it possible to implement session recording compression in Warpgate?

If not currently available, could this feature be considered for future versions?

This would greatly help optimize storage without losing valuable session data.

Thanks.

@Eugeny
Copy link
Member

Eugeny commented Jan 9, 2025

I've opened #1205 for this - but just in case you didn't know (it's not obvious), session recordings are also affected by the logs.retention config option - old sessions can be rotated away together with their recordings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants