AWS operators (S3, Redshift, EMR) in Apache Airflow - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the S3 operator in Airflow?

The S3 operator in Airflow helps automate tasks like uploading, downloading, or deleting files in Amazon S3 storage. It makes managing files in the cloud easy and automatic.

beginner

How does the Redshift operator in Airflow help with data workflows?

The Redshift operator runs SQL commands on Amazon Redshift clusters. It helps automate data loading, transformation, and querying tasks in a data warehouse.

intermediate

What is Amazon EMR and how does the EMR operator in Airflow interact with it?

Amazon EMR is a cloud service for big data processing using tools like Hadoop and Spark. The EMR operator in Airflow starts, monitors, and stops EMR clusters to run data jobs automatically.

intermediate

Why is it important to use AWS operators in Airflow instead of manual scripts?

AWS operators in Airflow provide reliable, repeatable, and easy-to-manage automation for cloud tasks. They handle errors and retries, making workflows more stable than manual scripts.

beginner

Name one best practice when using AWS operators in Airflow.

Use connection IDs and credentials stored securely in Airflow's connection manager instead of hardcoding keys. This keeps your cloud access safe and manageable.

Which Airflow operator would you use to upload a file to Amazon S3?

A EMRCreateJobFlowOperator

B RedshiftSQLOperator

C S3FileTransformOperator

D S3CreateBucketOperator

The S3FileTransformOperator is used to upload or transform files in S3. RedshiftSQLOperator runs SQL on Redshift, EMRCreateJobFlowOperator manages EMR clusters, and S3CreateBucketOperator creates buckets.

What does the Redshift operator in Airflow primarily execute?

A Run SQL queries on Redshift

B Start EMR clusters

C Upload files to S3

D Create S3 buckets

The Redshift operator runs SQL queries on Redshift clusters to manage data workflows.

Which AWS service does the EMR operator in Airflow control?

A Amazon S3

B Amazon Redshift

C Amazon RDS

D Amazon EMR

The EMR operator manages Amazon EMR clusters for big data processing.

Why should AWS credentials be stored in Airflow connections instead of hardcoded?

A To improve security and manageability

B To make code longer

C To slow down workflows

D To avoid using AWS

Storing credentials in Airflow connections keeps them secure and easy to update without changing code.

Which operator would you use to start an EMR cluster in Airflow?

A S3ListOperator

B EMRCreateJobFlowOperator

C RedshiftDataOperator

D S3DeleteObjectsOperator

EMRCreateJobFlowOperator starts EMR clusters. The others manage S3 or Redshift tasks.

Explain how Airflow AWS operators help automate cloud workflows for S3, Redshift, and EMR.

Think about what each AWS service does and how Airflow operators interact with them.

Describe best practices for securely using AWS operators in Airflow.

Focus on security and reliability in automation.

Practice

1. What is the primary purpose of the S3CreateObjectOperator in Airflow?

easy

A. To delete an S3 bucket

B. To list all objects in an S3 bucket

C. To create or upload an object (file) to an S3 bucket

D. To move objects between two S3 buckets

Solution

1. Step 1: Understand the operator's name and function

   The name S3CreateObjectOperator suggests it creates or uploads an object to S3.

2. Step 2: Match the operator to its main action

   This operator is designed to create or upload files to an S3 bucket, not delete or list buckets.

3. Final Answer:

   To create or upload an object (file) to an S3 bucket -> Option C

4. Quick Check:

   S3CreateObjectOperator = Upload file to S3 [OK]

Hint: Operator names usually describe their main action clearly [OK]

Common Mistakes:

• Confusing object creation with bucket deletion
• Thinking it lists objects instead of creating
• Assuming it moves objects between buckets

2. Which of the following is the correct way to instantiate an RedshiftSQLOperator in Airflow?

easy

A. RedshiftSQLOperator(sql='SELECT * FROM table', aws_conn_id='my_conn')

B. RedshiftSQLOperator(query='SELECT * FROM table', aws_conn_id='my_conn')

C. RedshiftSQLOperator(command='SELECT * FROM table', redshift_conn='my_conn')

D. RedshiftSQLOperator(sql='SELECT * FROM table', redshift_conn_id='my_conn')

Solution

1. Step 1: Identify correct parameter names for RedshiftSQLOperator

   The operator expects sql for the query and redshift_conn_id for the connection ID.

2. Step 2: Check each option for correct parameters

   RedshiftSQLOperator(sql='SELECT * FROM table', redshift_conn_id='my_conn') uses sql and redshift_conn_id, which is correct. Others use wrong parameter names.

3. Final Answer:

   RedshiftSQLOperator(sql='SELECT * FROM table', redshift_conn_id='my_conn') -> Option D

4. Quick Check:

   Use sql and redshift_conn_id for RedshiftSQLOperator [OK]

Hint: Remember: SQL query = sql, connection = redshift_conn_id [OK]

Common Mistakes:

• Using 'query' instead of 'sql' parameter
• Using 'aws_conn_id' instead of 'redshift_conn_id'
• Misspelling parameter names

3. Given the following Airflow task using EmrCreateJobFlowOperator:

emr_task = EmrCreateJobFlowOperator(
    task_id='start_emr_cluster',
    job_flow_overrides={
        'Name': 'TestCluster',
        'ReleaseLabel': 'emr-6.3.0',
        'Instances': {'InstanceCount': 3, 'KeepJobFlowAliveWhenNoSteps': True}
    },
    aws_conn_id='aws_default'
)

What will be the state of the EMR cluster after this task runs successfully?

medium

A. A running EMR cluster named 'TestCluster' with 3 instances, waiting for steps

B. An EMR cluster terminated immediately after creation

C. An EMR cluster with zero instances running

D. An error because 'ReleaseLabel' is missing

Solution

1. Step 1: Analyze job_flow_overrides parameters

   The cluster is named 'TestCluster', uses EMR release 6.3.0, has 3 instances, and is set to keep alive when no steps run.

2. Step 2: Understand KeepJobFlowAliveWhenNoSteps effect

   This setting keeps the cluster running after creation, waiting for steps to be added.

3. Final Answer:

   A running EMR cluster named 'TestCluster' with 3 instances, waiting for steps -> Option A

4. Quick Check:

   KeepJobFlowAliveWhenNoSteps=True means cluster stays running [OK]

Hint: KeepJobFlowAliveWhenNoSteps=True keeps cluster alive after creation [OK]

Common Mistakes:

• Assuming cluster terminates immediately
• Ignoring instance count setting
• Thinking ReleaseLabel is missing

4. You wrote this Airflow task to copy data from S3 to Redshift using RedshiftToS3Operator:

copy_task = RedshiftToS3Operator(
    task_id='copy_data',
    redshift_conn_id='redshift_default',
    s3_bucket='my-bucket',
    s3_key='data/output/',
    sql='SELECT * FROM users'
)

But the task fails with an error about missing parameters. What is the likely cause?

medium

A. The sql parameter is not supported by RedshiftToS3Operator

B. The operator name is incorrect; it should be S3ToRedshiftOperator

C. The s3_key parameter must be a full S3 URI starting with s3://

D. The redshift_conn_id must be named aws_conn_id

Solution

1. Step 1: Check operator purpose and name

   RedshiftToS3Operator copies data from Redshift to S3, but the task description says copying from S3 to Redshift.

2. Step 2: Identify correct operator for S3 to Redshift copy

   The correct operator for copying data from S3 to Redshift is S3ToRedshiftOperator.

3. Final Answer:

   The operator name is incorrect; it should be S3ToRedshiftOperator -> Option B

4. Quick Check:

   RedshiftToS3Operator copies Redshift to S3, not reverse [OK]

Hint: Check operator name matches data flow direction [OK]

Common Mistakes:

• Mixing up RedshiftToS3Operator and S3ToRedshiftOperator
• Assuming sql parameter works for all operators
• Incorrect S3 URI format

5. You want to automate a workflow where you first upload a CSV file to S3, then run a Redshift COPY command to load the data, and finally start an EMR cluster for processing. Which sequence of Airflow operators correctly implements this?

hard

A. S3CreateObjectOperator -> RedshiftSQLOperator -> EmrCreateJobFlowOperator

B. RedshiftSQLOperator -> S3CreateObjectOperator -> EmrCreateJobFlowOperator

C. EmrCreateJobFlowOperator -> S3CreateObjectOperator -> RedshiftSQLOperator

D. S3CreateObjectOperator -> EmrCreateJobFlowOperator -> RedshiftSQLOperator

Solution

1. Step 1: Identify the logical order of tasks

   First, upload the CSV to S3 using S3CreateObjectOperator.

2. Step 2: Load data into Redshift using COPY command via RedshiftSQLOperator

   After the file is in S3, run the COPY command in Redshift to load data.

3. Step 3: Start EMR cluster with EmrCreateJobFlowOperator for processing

   Finally, start the EMR cluster to process the loaded data.

4. Final Answer:

   S3CreateObjectOperator -> RedshiftSQLOperator -> EmrCreateJobFlowOperator -> Option A

5. Quick Check:

   Upload -> Load -> Process = A [OK]

Hint: Think data flow: upload, load, then process [OK]

Common Mistakes:

• Running Redshift load before uploading to S3
• Starting EMR before data is loaded
• Mixing operator order