Connect Server Setup Guide: Essential information missing from documentation


It'd be really great if the operator documentation for the connect server ( would cover the following topics:

  • Rationale for the server: Outline why you chose this architecture. It seems like a proxy. What is gained from having it? Caching/Reliability? Security/Isolation?
  • Setup recommendations: Outline where/how 1password would deploy the server for three most typical use cases. Same VPC? Same project? Inside the cluster you're providing with secrets? Run one per cloud provider you're using?
  • Sizing recommendations: Outline resource requirements for three most typical use cases.

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided


  • tback
    Community Member

    Some of my questions are answered in the technical overview for secret automation:

This discussion has been closed.