# Site-to-Site Site-to-site configurations are often unnecessary and should be avoided. If the only use for a site-to-site configuration is to provide remote users access to multiple sites creating a server at each site without linking will be more reliable and maintainable. Remote users can then connect to each site individually. If communication between servers at each site is required or users need to be able to connect to a single VPN server several services are available to interconnect networks such as AWS Direct Connect, Google Direct Peering and Azure ExpressRoute. These services partner with network providers using dedicated networks and hardware and will outperform any site-to-site VPN running on virtual instances. Additionally features such as replication are not available with linked servers. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.pritunl.com/kb/vpn/servers/site-to-site.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.