The following is only a selection of some of the major features we plan to implement in the near future. To get a more complete overview of planned features and current work, see the Approzium issue tracker.
Approzium currently runs on AWS as it uses the Security Token Service (STS) to authenticate applications. We plan to support the following cloud platforms soon:
- Google Cloud Platform
- Microsoft Azure
Approzium currently supports MySQL, MariaDB, Galera, MaxScale, Vitess, and PostgreSQL. These databases may be self-hosted, or a managed service such as AWS RDS and AWS Aurora. We plan to support the following databases:
Let us know if you would like to see support for any other self-hosted databases and DBaaS platforms.
Approzium currently supports Python applications. We plan to add other SDKs for the following programming languages in upcoming releases.
Both the SDK as well as the Authenticator service will support OpenTelemetry for generating logs, metrics and traces for enhanced observability. This will enable seamless support for tools such as ELK, Prometheus, Datadog and New Relic.
Secrets managers are used to store database credentials. Approzium currently works with Hashicorp Vault and AWS Secrets Manager. We plan to add support for the following secrets managers in the future.
- Google Cloud Secret Manager
- Azure Key Vault
- Kubernetes Secrets
Authenticator currently runs as a single instance of a docker container or one of the supported architecture specific binaries. We’re working on a high availability (HA) deployment model involving AWS auto scaling groups (ASG) that can be spun up using a choice of Terraform script or CloudFormation template. For Kubernetes deployments, support for Helm 3 charts is being added.