> ## Documentation Index
> Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy the service

> Deploy the Generic KMIP service in CryptoHub under dual control with TLS-bundle authentication.

Deploy a client-application service that owns the KMIP endpoint and its identity.

<Steps>
  <Step title="Open the template">
    Sign in to CryptoHub under dual control. Open **Services**, select the **Available Services** tab, select the **Generic** category, and select **Generic KMIP**.

    <Check>
      CryptoHub displays the template details with the **DEPLOY** and **DOCUMENTATION** actions.
    </Check>
  </Step>

  <Step title="Set up the service">
    Select **DEPLOY**. On the **Service Setup** step, enter a **Service Name** that identifies the KMIP application, keep the **Generic** service category, and select the **HSM Cluster** that protects the service keys. Select **NEXT**.

    <Check>
      The **Access Control** step opens.
    </Check>
  </Step>

  <Step title="Review access control">
    Review the **Authorized Resources** list. Under **Add Additional Resources**, add any other roles that must administer the service. Select **NEXT**.

    <Check>
      The **Service Info** step opens.
    </Check>
  </Step>

  <Step title="Deploy the service">
    Select **DEPLOY**.

    <Check>
      The service appears on the **Deployed Services** tab of the **Services** page.
    </Check>
  </Step>
</Steps>

<Note>
  The client certificate is the KMIP credential. The application does not need a username or password.
</Note>