@kapa.ai, I added following in values file for storing connector secrets in secrets manager. # Secrets Manager for Connector Secrets secretsManager: type: AWS_SECRET_MANAGER awsSecretManager: region: "us-east-1" authenticationType: "instanceProfile" And added secrets in secrets.yaml file Now, i get to see that I have 6 sources, 6 destinations and 6 connectors. But in secerts manager there are more than 100 airbyte secrets? Seems like it is not deleting old ? What to do?

This is a known issue with Airbyte's AWS Secrets Manager integration. There are a couple of reasons why secrets may accumulate: Why You Have More Secrets Than Expected 1. Versioning: Every time a connector configuration is updated, Airbyte increments the secret version (e.g.,

_v1

→

_v2

) and is supposed to delete the old version. If deletions are failing, old versions accumulate. [Secrets Docs] 2. Discover/Check temporary secrets: Airbyte creates temporary secrets with workspace ID

00000000-0000-0000-0000-000000000000

during Discover and Check operations, which are supposed to expire after 2 hours — but there is an open bug where these are not being cleaned up. [GitHub Issue] 3. Deletion on source/destination delete not working: There is an open bug where deleting a source via

DELETE /api/public/v1/sources/<source_id>

does not delete the corresponding AWS Secrets Manager secrets. The deletion code is reached but the secrets loop is skipped silently. [GitHub Issue] 4. Permission issue: Another reported cause is that Airbyte attempts to delete a secret using the wrong name (e.g., missing the

_v1

suffix), resulting in an

AccessDeniedException

from AWS. [GitHub Issue] What You Can Do • Check your IAM permissions: Ensure the instance profile role has

secretsmanager:DeleteSecret

permission scoped to Airbyte-managed secrets. The error logs in the

airbyte-server

pod will tell you if deletions are failing due to permissions. • Manually clean up: For now, you may need to manually identify and delete stale secrets in AWS Secrets Manager. Airbyte secrets follow the naming pattern:airbyte_workspace_workspace-id_secret_uuid_vversionSecrets with workspace ID

00000000-0000-0000-0000-000000000000

are temporary and safe to delete. • Monitor the open issues: Both bugs are currently open. You can track them at the GitHub links above and watch for fixes in upcoming Airbyte releases. • Check your Airbyte version: A related bug (secrets being deleted on update rather than preserved) was fixed in version 1.5. [Release Notes] Make sure you're on a recent version. Unfortunately, there is no automated workaround available at this time for the accumulation issue — it is an acknowledged bug in the open-source codebase. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Creating manually is not a solution. It's just 2 weeks at these are 100. Moving forward how to amke sure this doesn't ahppen again @kapa.ai

I understand the frustration — manual cleanup doesn't scale. However, I need to be transparent about what the knowledge sources tell us: Honest Assessment These are open, unresolved bugs in Airbyte's codebase: 1. Secrets not deleted when a source/destination is deleted [GitHub Issue] 2. Temporary Discover/Check secrets not expiring after 2 hours [GitHub Issue] The knowledge sources do not contain a confirmed fix or workaround that would prevent this from happening going forward. What You Can Do Right Now • Star/watch the open GitHub issues linked above so you're notified when a fix is released and can upgrade promptly. • Check your IAM role permissions — some users reported that adding

secretsmanager:DeleteSecret

to the instance profile role at least allows Airbyte to attempt deletions when the code path is reached. [GitHub Issue] • Set up an AWS lifecycle policy or tag-based cleanup rule in AWS Secrets Manager to automatically schedule deletion of secrets matching the

airbyte_workspace_00000000-0000-0000-0000-000000000000_*

pattern (temporary secrets), as those are safe to remove. Recommendation I'd suggest opening or commenting on the existing GitHub issues to increase visibility, and joining the Airbyte Community Slack to check if others have found interim solutions not yet documented. I'm sorry I can't offer a more definitive fix — the knowledge sources confirm this is an open bug without a documented resolution yet. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@Henry Mattingly, Any solution for this?

Based on the knowledge sources available to me, I can see partial progress but not a complete resolution: What Has Been Fixed • AWS Secrets Manager with tag-based IAM (ABAC): Airbyte 2.1 fixed a series of issues where AWS Secrets Manager operations failed with 500 errors for deployments using tag-based IAM policies, including better handling of

AccessDeniedException

. [Release Notes] Still Open • The core issue of secrets not being deleted when a source/destination is deleted remains an open GitHub issue with no confirmed fix documented in the knowledge sources. [GitHub Issue] • Temporary Discover/Check secrets not being cleaned up after 2 hours is also still open. [GitHub Issue] My Recommendation 1. Upgrade to the latest Airbyte version if you haven't already — the 2.1 IAM/ABAC fixes may help reduce some failure cases. 2. Check the open GitHub issues directly for the most up-to-date status, as the knowledge sources I have access to may not reflect the very latest developments. 3. Join the Airbyte Community Slack to ask if others on recent versions are still experiencing this. I'm sorry I can't give a more definitive answer — the knowledge sources do not confirm a full resolution to the secret deletion problem. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@Mark Grivnin @Alex Cuoci Can anyone help me with this? I woke up today with 93 orphan secrets in AWS Secrets Manager that is impacting cost. Secrets which has "00000000-0000-0000-0000-000000000000" in their name. Any solution so far?

How can I help you with your Airbyte deployment? If you are looking for specific next steps regarding your AWS Secrets Manager issue, here is what you can do: 1. Verify IAM Permissions: Ensure your AWS IAM policy explicitly allows the

secretsmanager:DeleteSecret

action on the resources [GitHub Issue]. 2. Automate Temporary Secret Cleanup: You can create an external scheduled AWS Lambda function or script to periodically find and delete orphaned Discover/Check secrets matching the placeholder workspace ID

airbyte_workspace_00000000-0000-0000-0000-000000000000_*

[Secrets Docs]. 3. Upgrade Airbyte: Upgrade to the latest release to ensure you have all recent bug fixes related to secret handling and AWS Secrets Manager. Please let me know if you need help with a specific configuration, log analysis, or another aspect of Airbyte! 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements