FusionAuth is an API first Customer Identity and Access Management (CIAM) platform.

With support for OAuth2, OIDC, SAML v2, social login, federated login, MFA, full text search, password policies, WebAuthn, and other passwordless options FusionAuth checks all of your boxes.

Add enterprise quality authentication and authorization to your application by deploying FusionAuth via 1-Click.

Software Included

Package Version License
FusionAuth 1.47.1 Free

Creating an App using the Control Panel

Click the Deploy to DigitalOcean button to install a Kubernetes 1-Click Application. If you aren’t logged in, this link will prompt you to log in with your DigitalOcean account.

Deploy to DO

Creating an App using the API

In addition to creating FusionAuth using the control panel, you can also use the DigitalOcean API. As an example, to create a 3 node DigitalOcean Kubernetes cluster made up of Basic Droplets in the SFO2 region, you can use the following doctl command. You need to authenticate with doctl with your API access token) and replace the $CLUSTER_NAME variable with the chosen name for your cluster in the command below.

doctl kubernetes clusters create --size s-4vcpu-8gb $CLUSTER_NAME --1-clicks fusionauth

Getting Started After Deploying FusionAuth

Once the FusionAuth stack is installed in the DigitalOcean 1-Click Apps Marketplace you should:

  1. Run helm list -n fusionauth to confirm stack was deployed. You should have 3 deployments: db, fusionauth, search.
  2. Check running pods and their status with: kubectl get pods -n fusionauth
  3. Connect to your cluster via the command line.
  4. To visit FusionAuth, enter the following into the command line:

export SERVICE_IP=$(kubectl get svc –namespace fusionauth fusionauth -o jsonpath=’{.status.loadBalancer.ingress[0].ip}')

echo Visit http://$SERVICE_IP:9011/ to access the FusionAuth console.

Once you see the setup-wizard in the browser, follow the initial setup guide by following this link. https://fusionauth.io/docs/v1/tech/tutorials/setup-wizard

For development or testing purposes, a single node may be sufficient. A node count of 3 or more is recommended for a production deployment.