AWS Certified Data Analytics Specialty 2021 – Hands-On - (Exercise) Kinesis Firehose, Part 3

The video tutorial guides users through setting up an AWS Kinesis Firehose endpoint, managing permissions, and attaching an IAM role to an EC2 instance. It also covers configuring data flows and starting the Kinesis agent to monitor and transfer log data to Amazon S3. The tutorial emphasizes security best practices and provides step-by-step instructions for each process.

What should you do if your Firehose endpoint is not in the default region?

• Use a different AWS service.

• Ignore it, as it will automatically adjust.

• Specify the region explicitly in the settings.

• Contact AWS support for assistance.

Why is using IAM roles preferred over access keys for permissions?

• IAM roles are easier to remember.

• Access keys are more secure.

• IAM roles reduce the risk of exposing credentials.

• Access keys are deprecated.

What is the purpose of configuring the Kinesis agent?

• To update AWS security settings.

• To manage AWS billing.

• To create new EC2 instances.

• To monitor a log directory and send data to Firehose.

How can you ensure the Kinesis agent starts automatically?

• By using the AWS console.

• By configuring the agent to start on boot.

• By manually starting it each time.

• By setting a cron job.

What does the Firehose policy dictate regarding data storage?

• Data is stored every 10 minutes.

• Data is stored every 5 MB or 60 seconds, whichever comes first.

• Data is stored only when manually triggered.

• Data is stored in a single large file.

What format is the data stored in S3 after being processed by Firehose?

• Plain text

• CSV

• XML

• JSON

What is the final step to verify the data transfer to S3?

• Review the log files in the AWS console.

• Check the AWS billing dashboard.

• Restart the EC2 instance.

• Open the S3 bucket and inspect the data.