A company is designing a solution to capture customer activity in different web applications to process analytics and make predictions. Customer activity in the web applications is unpredictable and can increase suddenly. The company requires a solution that integrates with other web applications. The solution must include an authorization step for security purposes. Which solution will meet these requirements?

The correct solution uses Amazon API Gateway, Kinesis Data Firehose, S3, and a Lambda authorizer. API Gateway provides a scalable, integrated endpoint for web applications, handling the unpredictable activity. Kinesis Data Firehose is designed for streaming data ingestion, automatically scaling to handle fluctuating loads and delivering data to S3 for storage and analytics. An API Gateway Lambda authorizer provides a robust and customizable authorization step, meeting the security requirement. Incorrect options: Using a Gateway Load Balancer (GWLB) is for deploying, scaling, and managing virtual appliances, not for direct web application integration or data ingestion. Storing data directly in Amazon EFS from a container instance isn't ideal for high-throughput, unpredictable streaming data. Resolving authorization at the GWLB is not a standard or efficient pattern for application-level authorization. While Amazon Kinesis Data Streams can handle streaming data, Kinesis Data Firehose is generally simpler for direct delivery to S3 without needing to manage shards or consumers, making it a better fit for this scenario. Using a separate Lambda function for authorization instead of an API Gateway Lambda authorizer adds unnecessary complexity and integration points.