IoTeX Delegate Documentation
  • Introduction
    • 👋 Welcome
    • What is a Delegate
    • Benefits and Rewards
    • Delegate Requirements
    • Hardware Specs
  • Get Started
    • Profile registration
      • Delegate Accounts
      • Name Registration
      • Staking Bucket
      • Server Information
      • Rewards Policy
      • Profile Data
    • Node Configuration
      • Acquire a server
      • Install requirements
      • Install the node software
      • Run the node
      • Verify the node status
    • Advanced
      • Server provider
      • Edge Proxy
      • Kubernetes
      • High Availability
      • Gravity Chain Binding
      • Improvements
    • Hosted Service
    • Delegate Endorsement
      • Delegate Sponsorship Program
      • Tutorials
  • Delegate Management
    • Access the portal
    • Delegate Performance
    • Delegate Rewards
    • Profile settings
    • Advanced Configuration
  • Addendum
    • Profits Projections
    • Glossary
Powered by GitBook
On this page
  1. Get Started
  2. Advanced

Edge Proxy

PreviousServer providerNextKubernetes

Last updated 3 years ago

Run your node behind an edge proxy like Envoy

combined with provides request rate limiting on HTTP/HTTP2 and connection limits on all network traffic. Putting your IoTeX node behind an Envoy proxy gives you another layer of protection against attackers, especially if you intend to use your node and an IoTeX API gateway.

Additionally, since the IoTeX node API utilizes GRPC, if you want to be an IoTeX service node and serve API requests to in-browser applications, you will need Envoy's filter enabled for this functionality.

Below you find an example configuration file for Envoy where we set the max connection numbers to 50 and enabled the rate limit for HTTP requests (find the respective rate limit configuration file below):

Envoy
rate limit
grpc-web