Vectice Docs
API Reference (Latest)Vectice WebsiteStart Free Trial
Latest
Latest
  • 🏠Introduction
    • Vectice overview
      • Autolog
      • Next-Gen Autolog [BETA]
      • AskAI
      • Vectice for financial services
  • 🏁Quickstart
    • Getting started
    • Quickstart project
    • Tutorial project
    • FAQ
  • ▶️Demo Center
    • Feature videos
  • 📊Manage AI/ML projects
    • Organize workspaces
      • Create a workspace
      • Workspace Dashboard
    • Organize projects
      • Create a project
      • Project templates best practices
    • Invite colleagues
    • Define phase requirements
    • Collaborate with your team
  • 🚀Log and Manage Assets with Vectice API
    • API cheatsheets
      • Vectice Python API cheatsheet
      • Vectice R API cheatsheet
    • Connect to API
    • Log assets to Vectice
      • Autolog your assets
      • Log datasets
      • Log models
      • Log attachments and notes
      • Log code
      • Log a custom data source
      • Log assets using Vectice IDs
      • Log dataset structure and statistics
      • Log custom metadata in a table format
      • Log MLFLow runs
    • Retrieve assets from app
    • Manage your assets
    • Manage your iteration
    • Preserve your code and asset lineage
  • 🤝Create Model documentation and reports
    • Create model documentation with Vectice Reports
    • Streamline documentation with Macros
    • Auto-document Models and Datasets with AskAI Prompts
    • Document phase outcomes
  • 🗂️Admin Guides
    • Organization management
    • Workspace management
    • Teams management
    • User management
      • User roles and permissions
      • Update a user role in your organization
      • Activate and deactivate users
      • Reset a user's password
    • Manage report templates
  • 🔗Integrations
    • Integrations Overview
    • Integrate Vectice with your data platform
  • 💻IT & Security
    • IT & Security Overview
    • Secure Evaluation Environment Overview
    • Deployment
      • SaaS offering (Multi-Tenant SaaS)
      • Kubernetes self-hosted offering
        • General Architecture & Infrastructure
        • Kubernetes on GCP
          • Appendices
        • Kubernetes on AWS
          • Appendices
        • Kubernetes on Azure
          • Appendices
        • GCP Marketplace deployment
        • On premise
        • Configuration
      • Bring Your Own LLM Guide
    • Data privacy
    • User management
    • SSO management
      • Generic SAML integration
      • Okta SSO integration
    • Security
      • Data storage security
      • Network Security
        • HTTPS communication
        • Reverse proxy
        • CORS/CSRF
        • VPC segregation
      • Sessions
      • Secrets and certificates
      • Audit logs
      • SOC2
      • Security updates
      • Best practices
      • Business continuity
    • Monitoring
      • Installation guide
      • Customizing the deployments
    • Maintenance & upgrades
    • Integrating Vectice Securely
  • ⭐Glossary
    • Concepts
      • Workspaces
      • Projects
        • Setup a project
      • Phases
      • Iterations
        • Iterative development
      • Datasets
        • Dataset resources
        • Dataset properties
        • Dataset lineage and versions
      • Models
      • Reports
  • 🎯Release notes
    • Release notes
  • ↗️References
    • Vectice Python API Reference
    • Vectice R API Cheatsheet
    • Notebooks and code samples
    • Vectice website
Powered by GitBook
On this page
  • Load balancing with enhanced security
  • Simplified traffic management and enhanced security
  • Performance and scalability

Was this helpful?

  1. IT & Security
  2. Security
  3. Network Security

Reverse proxy

PreviousHTTPS communicationNextCORS/CSRF

Last updated 1 year ago

Was this helpful?

Load balancing with enhanced security

For self-hosted Vectice deployments, we recommend using a secure load-balancing solution such as , , or . Our SaaS offering comes pre-configured with this setup.

Simplified traffic management and enhanced security

  • Single entry point: The Load Balancer is a single entry point for all incoming traffic. This centralized approach simplifies traffic management and efficiently routes requests to the appropriate backend services within the cluster.

  • Restricted access: We take security further by restricting incoming traffic to designated ports and protocols. This additional control layer minimizes the attack surface and strengthens our security posture.

  • HTTPS enforcement: By default, the Load Balancer can be configured to enforce HTTPS encryption for all incoming traffic. This ensures your data is always encrypted in transit, safeguarding it from potential interception.

  • Granular access control: We can implement granular access control rules within the Load Balancer, restricting access to specific services or resources based on predefined criteria. This provides an extra layer of security.

Performance and scalability

  • High performance: Load Balancers are known for their scalability and high-performance capabilities. This ensures our platform can efficiently handle fluctuating traffic volumes, maintaining a smooth user experience.

Combined, Load balancing, which focuses on secure communication protocols and port restrictions, along with a Kubernetes Ingress for traffic management, delivers a robust and secure solution for accessing our software.

💻
Application Gateway (Azure)
AWS Load Balancer
Google Kubernetes Engine Load Balancer