In Astro, certain environment variables have preset values that are required and should not be overridden by your organization. The following table provides information about each global environment variable set by Astronomer.
For information on setting your own environment variables, see Environment variables.
The Cloud UI does not currently prevent you from setting these environment variables, but attempting to set them can result in unexpected behavior that can include access problems, missing task logs, and failed tasks.
If you need to set one of these variables for a particular use case, contact Astronomer support.
System environment variables
|Routes scheduler logs to stdout|
|Enables remote logging|
|Location of remote logging storage|
|Connection URI for writing task logs to Astro's managed S3 bucket|
|Determines whether to use server-side encryption for S3 logs|
|The base URL of the Airflow UI|
|The SqlAlchemy connection string for the metadata database|
|Determines whether to update FAB permissions on webserver startup|
|Determines whether to enable werkzeug ProxyFix middleware for reverse proxy|
|The connection ID for accessing the Airflow metadata database|
|The secret key for saving connection passwords in the metadata database|
|The executor class that Airflow uses. Astro exclusively supports the Celery executor|
|The home directory for an Astro project|
|The Kubernetes namespace where Airflow workers are created|
|Path to a callable, which resolves to the hostname|
|Determines whether Statsd is on|
|The hostname for Statsd|
|The port for Statsd|
|Determines whether metrics are sent to Statsd|
|The hostname for sending metrics to Statsd|
|The port for sending metrics to Statsd|
|Sets a |
|Shows the name of your Deployment in the Home view of the Airflow UI|
|Determines how many tasks each Celery worker can run at any given time and is the basis of worker auto-scaling logic|
|The color of the main navigation bar in the Airflow UI|
|Exposes the Configuration tab of the Airflow UI and hides sensitive values|
|The key secret for accessing Astro's managed S3 bucket¹|
|The URL for your Astro lineage backend. The destination for lineage data sent from external systems to the OpenLineage API.|
|Your OpenLineage API key|
AWS_ACCESS_KEY_ID environment variables are required only for Deployments running on AWS. For any Deployment running on an AWS cluster, they should not be overridden.
There are no restrictions with setting these values for Deployments running on GCP and Azure.