Providers for Apache Airflows
Airflow providers are separately installed packages that add operators, hooks and sensors for external systems such as AWS, Google Cloud, Postgres or Snowflake. Connections store the host, login and secrets for those systems in Airflow, so DAG code refers to a connection id rather than embedding credentials.
Stage: Integrations · Part of the Apache Airflow roadmap · Last reviewed 19 November 2026
What to learn in Providers
- Install a provider package and import its operators
- Create a connection in the UI or through an environment variable
- Use a hook to run a query against a database
- Wait for a file or partition with a sensor
- Store secrets in a secrets backend rather than in DAG code
Providers interview questions
What is the difference between an operator and a hook?
A hook is a low-level interface to an external system that manages the connection and exposes methods. An operator is a task template that usually uses a hook to do one action. Write a custom hook when you need reusable access logic, and use operators for the task itself.
How should credentials be handled in Airflow?
Store them in Airflow connections, ideally backed by a secrets manager or environment variables, and reference them by connection id in DAGs. Never hard-code passwords in DAG files or commit them to Git. Connection fields are encrypted in the metadata database when a Fernet key is configured.
Where Providers fits in the Apache Airflow roadmap
Providers belongs to the Integrations stage (intermediate level). Connect systems.
Other units in this stage
Back to the full Apache Airflow roadmap