Example of Agent with tools hosted on ECS Fargate

[darenwkt]

Amazon Bedrock Agent Samples Pull Request

Instructions

• Do not erase any parts of this template that are not applicable to your pull request.
• If a section is not applicable, explicitly state the reason.
• • Tick the checkboxes for the items you have completed.
• These are mandatory requirements, not mere suggestions.

---

Describe your changes

• Concise description of the PR

Add a new example of building Agent with tools (Apache Tika) hosted on ECS Fargate

---

Issue ticket number and link

• Issue # (if applicable) Amazon Bedrock Agent Samples - [Agent with tools hosted on AWS ECS Fargate] #181

---

All Submissions:

• Have you followed the guidelines in our Contributing document? Yes
• Have you checked to ensure there aren't other open Pull Requests for the same update/change? Yes
• Are you uploading a dataset? No
• Have you added contributions to RELEASE NOTES?

---

New Example Submissions:

• Have you tested your code, and made sure the functionality runs successfully? Provide screenshots.

• User can prompt bedrock agent to analyse their files in S3 using Apache Tika hosted on AWS ECS Fargate

• Have you linted your Python code with black?

• Does this implementation use the shared tools src/utils/*. List them here: N/A

• Does this implementation use the helper functions src/utils/*. List them here:

• Have you included your Agent Example name and introduction in README.md and examples/agents/README.md? Yes

• Have you included your Multi-Agent Example name and introduction in README.md and examples/multi_agent_collaboration/README.md? N/A

• Have you documented Introduction, Architecture Diagram, Prerequisites, Usage, Sample Prompts, and Clean Up steps in your example README?

• I agree to resolve any issues created for this example in the future.

---

src/utils Submissions:

Changes to the utils folder won't be accepted. Instead, open a new issue.

---

src/shared tool Submissions:

Changes to existing tools won't be accepted. Instead, open a new issue.

• Business justification for including a new tool

This tool is necessary because it addresses a recurring community need — hosting Apache Tika on AWS has been a common question (see [StackOverflow: Run Tika Server in AWS Lambda](https://stackoverflow.com/questions/45626105/run-tika-server-in-aws-lambda) and [AWS Post](https://repost.aws/questions/QUfS7tZ_LqTIy9Uf1NhMHB_A/extract-file-metadata)), and internally at AWS we have seen customers adopting this pattern as well (Feel free to reach out privately to understand the internal customer needs or use cases). 

More details available in: #181

• How is this tool implemented?
  • • AWS CDK
  • • AWS CloudFormation (recommended)

---

• Add your name to CONTRIBUTORS.md :D

[darenwkt]

Thanks @jdebuseamazon for the comments, have addressed them, please take another look! 🙏

[darenwkt]

Thanks @jdebuseamazon, addressed latest comments, could you take another look please? 🙏

[jdebuseamazon]

Many thanks for addressing all the comments! 🚢😀

[darenwkt]

Thanks @jdebuseamazon for the review! @EashanKaushik would you be able to kindly review this PR as well please? 🙏