Migrating an existing EC2 + Docker deployment of Airbyte to a Helm deployment involves several steps. Here's a general guide based on the information provided in the knowledge sources: 1. Prerequisites: Ensure you have access to your Kubernetes cluster where Airbyte will be deployed. You should have Helm and kubectl installed and configured on your machine. You should also have an existing Airbyte deployment using AWS S3 for storage and AWS Secrets Manager for secret management. [source](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#prerequisites) 2. Creating or Updating Kubernetes Secrets: If you're using AWS access keys, create a Kubernetes secret to store these credentials. If you're relying on an IAM role from an instance profile, you can skip this step. Here's an example of how to create a Kubernetes secret with your AWS credentials:

yaml apiVersion: v1   kind: Secret   metadata:     name: airbyte-config-secrets   type: Opaque   stringData:     s3-access-key-id: AKIAIOSFODNN7EXAMPLE # Enter your AWS Access Key ID here     s3-secret-access-key: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY # Enter your AWS Secret Access Key here

[source](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#migration-steps-1) 3. Update Airbyte Configuration: In your

airbyte.yml

configuration file, add the following configuration, adjusting

<aws-region>

to match your AWS region:

yaml global:     storage:       type: s3       storageSecretName: airbyte-config-secrets       bucket:         log: airbyte-storage         state: airbyte-storage         workloadOutput: airbyte-storage       s3:         region: <aws-region>         authenticationType: credentials # Use "credentials" or "instanceProfile"         accessKeyIdSecretKey: aws-secret-manager-access-key-id # Omit if using instanceProfile         secretAccessKeySecretKey: aws-secret-manager-secret-access-key # Omit if using instanceProfile        secretsManager:       type: awsSecretManager       storageSecretName: airbyte-config-secrets       awsSecretManager:         region: <aws-region>         authenticationType: credentials # Use "credentials" or "instanceProfile"         accessKeyIdSecretKey: aws-secret-manager-access-key-id # Omit if using instanceProfile         secretAccessKeySecretKey: aws-secret-manager-secret-access-key # Omit if using instanceProfile         tags:           - key: team             value: deployment           - key: business-unit             value: engineering

[source](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#migration-steps-1) 4. Deploy Airbyte: If you don't intend to customize your deployment, you can deploy Airbyte as is with default values. Run the following command:

bash helm install %release_name% airbyte/airbyte

Note:

release_name

should only contain lowercase letters and optionally dashes (

release_name

must start with a letter). [source](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#default-deployment) Please note that this is a general guide and the exact steps may vary depending on your specific setup and requirements. Always refer to the official Airbyte documentation for the most accurate and up-to-date information.