Add cloud-based auth (aws_iam, gcp, azure_ad) to Akeyless secrets backend#69772
Merged
eladkal merged 3 commits intoJul 12, 2026
Merged
Conversation
The secrets backend previously only supported api_key and uid auth. This adds aws_iam, gcp, and azure_ad authentication using the akeyless_cloud_id package, enabling seamless integration with managed Airflow services like Amazon MWAA, GCP Cloud Composer, and Azure workloads without requiring static API keys. Co-authored-by: Cursor <cursoragent@cursor.com>
boring-cyborg
Bot
added
area:providers
area:secrets
kind:documentation
provider:akeyless
labels
Cloud Composer was rebranded to Managed Service for Apache Airflow (Managed Airflow) as of April 2026. Co-authored-by: Cursor <cursoragent@cursor.com>
joshuabvarghese
pushed a commit
to joshuabvarghese/airflow
that referenced
this pull request
Jul 16, 2026
…kend (apache#69772) * Add cloud-based auth (aws_iam, gcp, azure_ad) to AkeylessBackend The secrets backend previously only supported api_key and uid auth. This adds aws_iam, gcp, and azure_ad authentication using the akeyless_cloud_id package, enabling seamless integration with managed Airflow services like Amazon MWAA, GCP Cloud Composer, and Azure workloads without requiring static API keys. Co-authored-by: Cursor <cursoragent@cursor.com> * Update Cloud Composer references to Managed Service for Apache Airflow Cloud Composer was rebranded to Managed Service for Apache Airflow (Managed Airflow) as of April 2026. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
aws_iam,gcp, andazure_adauthentication support toAkeylessBackendsecrets backend, enabling seamless integration with managed Airflow services (Amazon MWAA, GCP Cloud Composer, Azure) without requiring static API keys.akeyless_cloud_idpackage (already an extra dependency of the provider) to generate cloud identity tokens, reusing the same pattern already implemented inAkeylessHook.Motivation
The Akeyless secrets backend previously only supported
api_keyanduidauthentication. Users on managed Airflow services like Amazon MWAA naturally expect to authenticate using their environment's IAM role rather than managing static API keys. This change closes that gap.Changes
providers/akeyless/src/airflow/providers/akeyless/secrets/akeyless.py_SUPPORTED_BACKEND_AUTH_TYPESto includeaws_iam,gcp,azure_ad_get_cloud_id()method for cloud identity token generation_authenticate()to route cloud auth types through_get_cloud_id()gcp_audience,azure_object_id)providers/akeyless/tests/unit/akeyless/secrets/test_akeyless.pyCloudIdintegration, parameter passthrough, and missing-package error handlingproviders/akeyless/docs/secrets-backend.rstgcp_audience,azure_object_id,token_ttlto parameters tableTest plan
akeyless_cloud_idpackage raises clearImportErrorMade with Cursor