Trust Providers enable Aembit to authenticate without provisioning credentials or other secrets. Trust Providers are third-party systems or services that can attest identities with identity documents, tokens, or other cryptographically signed evidence.
Client Workload identity attestation is a core functionality to ensure only trusted Client Workloads can access the Server Workloads.
Configure Trust Provider
Section titled “Configure Trust Provider”If you are getting started with Aembit, configuring trust providers is optional; however, it is critical to secure all production deployments.
-
Click the Trust Providers tab.
-
Click + New to create a new Trust Provider.
-
Give the Trust Provider a name and optional description.
-
Choose the appropriate Trust Provider type based on your Client Workloads’ environment.
-
Follow the instructions for the Trust Provider based on your selection.
- AWS Role Trust Provider
- AWS Metadata Service Trust Provider
- Azure Metadata Service trust provider
- Kerberos trust provider
- Kubernetes Service account trust provider
- Configure one or more match rules (specific to your Trust Provider type).
- Click Save.
Client Workload Identity Attestation
Section titled “Client Workload Identity Attestation”You must associate one or more Trust Providers with the existing Access Policy for Aembit to use Client Workload identity attestation.
-
Choose one of the existing Access Policies.
-
Click Edit.
-
Add an existing, or create a new Trust Provider.
Agent Controller Identity Attestation
Section titled “Agent Controller Identity Attestation”You must associate a Trust Provider with Agent Controller in order for Aembit to use Agent Controller for identity attestation.
-
Click the Edge Components tab.
-
Select one of the existing Agent Controllers.
-
Click Edit.
-
Choose from the dropdown one of the existing Trust Providers.