> For the complete documentation index, see [llms.txt](https://docs.islandrouter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.islandrouter.com/island-router-cli-2.3.2/commands/vpn-peer/vpn-peer-public-key.md). # vpn peer public-key Specify a VPN peer's public key. ## Syntax ``` [no] vpn peer public-key ``` ## Syntax Description
KeywordDescription
no(Optional) Removes the peer public key from the VPN.
idThe VPN identifier. Must be a number in the range 0-1022 or the keyword "auto".
keyThe peer's public key
## Defaults None; a peer's public key must be defined before communcations can take place. ## Usage Guidelines Each end of a WireGuard VPN has a public/private key pair. The private key is known only to that end, while the public key is shared with the VPN's peer(s). This command provides Island with a VPN peer's public key. If a VPN exists with the specified identifier, the existing VPN will be modified; otherwise, a new VPN with the specified identifier will be created. If "auto" is specified for the identifier, a new VPN will be created using the next available identifier. ## Examples ``` vpn peer auto public-key 7cNt7EEQVVWVWh+63xY5+dU7uDGZk2IRKENcchJPuS0= ``` ## Related Commands --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.islandrouter.com/island-router-cli-2.3.2/commands/vpn-peer/vpn-peer-public-key.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.