A company uses an AWS Batch job to run its end-of-day sales process. The company needs a serverless solution that will invoke a third-party reporting application when the AWS Batch job is successful. The reporting application has an HTTP API interface that uses username and password authentication.
Which solution will meet these requirements?
The best solution to meet the requirements is to configure an Amazon EventBridge rule to match incoming AWS Batch job SUCCEEDED events and set the third-party API as an EventBridge API destination with a username and password. EventBridge can directly handle the authentication and invoke the third-party reporting application without additional services, ensuring the process remains fully serverless and minimizes complexity.
https://aws.amazon.com/blogs/compute/using-api-destinations-with-amazon-eventbridge/ Amazon EventBridge enables developers to route events between AWS services, integrated software as a service (SaaS) applications, and your own applications. It can help decouple applications and produce more extensible, maintainable architectures. With the new API destinations feature, EventBridge can now integrate with services outside of AWS using REST API calls.
I agree.
I'm confused. Both A and B seem to be viable. There is no requirement of cost, complexity, or overhead. :S
A. Configure an Amazon EventBridge rule to match incoming AWS Batch job SUCCEEDED events. Configure the third-party API as an EventBridge API destination with a username and password. Set the API destination as the EventBridge rule target. This option is the most direct and serverless approach to meeting the requirements. Amazon EventBridge can detect the successful completion of the AWS Batch job and trigger actions based on this event. By configuring the third-party API as an API destination with authentication credentials, EventBridge can directly invoke the third-party reporting application without the need for additional services. This approach minimizes complexity and operational overhead.
I think is better to programming a lambda and obtain user and password from Secret Manager... So I think the better solution is B
EventBridge also store credentials in Secret manager: https://aws.amazon.com/blogs/compute/using-api-destinations-with-amazon-eventbridge/
Create an AWS Lambda function responsible for invoking the third-party reporting application's HTTP API endpoint. The Lambda function will be triggered by the successful completion of the AWS Batch job.
Configure Amazon EventBridge Scheduler to match incoming AWS Batch job SUCCEEDED events. Configure an AWS Lambda function to invoke the third-party API using a username and password. Set the Lambda function as the EventBridge rule target.
AWS Batch sends job status change to EventBridge. https://docs.aws.amazon.com/batch/latest/userguide/batch_cwe_events.html
AnswerA EventBridge Schedule will not work as it will allow us to "do something" per schedule. EventBridge rule will allow us to "do something" when event will occur. I think there is no possibility to publish/send job "SUCCEEDED" to AMAZON API Gateway REST API or that we can do anykind of integration with AMAZON API Gateway, hence I would choose A
Even though option A and B could do the trick and also no statement related to least effort is rquested, EventBridge is dedicated for similar use case. https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destinations.html Plus, it can also handle basic authentication https://aws.amazon.com/blogs/compute/using-api-destinations-with-amazon-eventbridge/
Answer should be B.
look like B