Overview
In order to enable Axiom to manage access requests to a system (such as AWS, GitHub, Kubernetes, PostgreSQL, etc.), you must first create a connection between the system and Axiom.
We call this connection - "integration."
Integrations typically take only a few minutes to set up.
Supported Integration Types
Below are step-by-step setup guides tailored to the system you wish to integrate with Axiom:
Cloud
Identity Provider (IDP)
One Login - Coming soon
Databases
Snowflake - Coming soon
Other
On-call
These special integrations allow the use of oncall rota information in Axiom automated workflows but do not manage access to these systems.
💡 If you wish to remove an integration, you can use this step-by-step guide
Additional Information
Every integration type appears as a System in Axiom:
You may have more than one integration per type. You will need a separate integration for each:
AWS account
GCP or Azure account
GWS, Jumpcloud, Entra ID, or Okta account
MongoDB Atlas endpoint
MySQL project
PostgreSQL server
Kubernetes cluster
View Resources Across Integrations
When making access requests using Axiom, users will see all Targets (the resources for which they want access), from all integrations of the same type.
For example, if you have two AWS organizations integrated, your users only need to know to select AWS as the "System" and would then see resources from both of these integrations (assuming the user has the required Scope).
