Apache Tika Server, a REST service that detects file types and extracts text and metadata from documents in over a thousand formats.
Apache Tika Server is the standalone HTTP interface to the Apache Tika toolkit, exposing content detection and extraction over a simple REST API. Send it a document, PDF, Office file, email, image or one of more than a thousand supported formats, and it returns the plain text content and a structured set of metadata such as author, title, dates and the detected media type. It is stateless, holding no data between requests, which makes it a natural building block in search indexing, document processing and retrieval augmented generation pipelines that need to turn arbitrary files into clean, machine readable text. Backed by the mature PDFBox and Apache POI parsers, it handles the messy variety of real world documents so applications do not have to.
The cloudimg image is hardened and fully patched with Apache Tika Server preconfigured as a dedicated non root service bound to loopback and never exposed directly. It ships secure by default: the Tika API is fronted by nginx which terminates TLS with a certificate generated uniquely on every instance and enforces HTTP Basic Auth, the dangerous file fetching and unpack features stay disabled to close the metadata request forgery path, instance metadata service version two is enforced, and heap, memory and upload size limits contain oversized or malicious uploads. No credential and no usable certificate are baked in: on first boot every instance generates its own Basic Auth password and its own certificate, so no two deployments share a secret. Every instance is backed by a paired deploy guide and 24/7 cloudimg support.
This is a repackaged open source software product wherein additional charges apply for cloudimg support services.
## Text and Metadata Extraction as a Service
Apache Tika is the Apache Software Foundation's content detection and extraction toolkit. It detects and extracts text and metadata from thousands of file types - PDF, Microsoft Office and OpenDocument, HTML, RTF, EPUB, images, email and archive formats - through one consistent REST API. This image runs Tika Server 3.3.1 on OpenJDK 17 as a hardened, stateless service, so you can turn a document into clean text or structured metadata within minutes of launch rather than assembling a parser stack yourself.
## Who This Is For
Search and data teams building a document ingestion pipeline who need reliable text extraction as the first stage. AI and RAG builders who need to turn PDFs, spreadsheets and slide decks into plain text before chunking and embedding. Application developers who need a standards-based extraction endpoint to call from their own services instead of bundling dozens of parser libraries.
## What Is Installed
## Secure By Default
Tika Server has no built-in authentication and a real history of parser CVEs, so this image does not expose it directly:
## Network Model
The shipped security group opens only port 22. The HTTPS listener on port 443 is not exposed by default. Add a port 443 ingress rule scoped to your own network when you are ready, or reach the service over an SSH tunnel. The user guide covers both, along with pointing an upstream load balancer or your own certificate at the service.
## Getting Started
1. Launch the image on an m5.large instance or larger, with port 22 open to your management network
2. Connect over SSH as the default login user for your variant (the user guide lists it)
3. Retrieve the generated API password with sudo cat /root/tika-server-credentials.txt
4. Extract text from a document: curl -u admin:PASSWORD -k -T report.pdf -H 'Accept: text/plain' https://INSTANCE/tika
5. Extract metadata as JSON from the /meta endpoint, or recursive text and metadata from /rmeta
6. Add a port 443 rule scoped to your network, or front the service with your own load balancer and certificate
## 24/7 cloudimg Support
Every deployment is backed by cloudimg engineers available around the clock by email and live chat. Support covers deployment and sizing guidance, tuning the JVM heap and Tika configuration for your document mix, enabling OCR or additional parsers, wiring Tika into a search or retrieval-augmented-generation pipeline, TLS certificate and reverse proxy configuration, credential management, and Tika upgrades and troubleshooting. Critical issues receive a one-hour average response time.
## Evaluation
This image uses standard AWS pay-as-you-go infrastructure billing. Launch an instance to evaluate extraction against your own documents, and terminate at any time.
Apache, Apache Tika and Tika are trademarks of The Apache Software Foundation. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.