Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Default deploy installs eoapi-cdk 10.3.0, whose STAC runtime fails to import (`No module named 'stac_fastapi.extensions.core.fields'`)

Open Beginner friendly
#46 1 comment 0 reactions 0 assignees View on GitHub

@hrodmn is already working on this.

Since Jul 1, 2026.

  • #48 by @hrodmn — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
aws, python
Domain
cloud, devops

Research direction

Start with the eoapi-cdk constraint in pyproject.toml and the resolved version in uv.lock; run uv sync to confirm the dependency resolution. Update the dependency so a fresh deploy no longer selects 10.3.0, then run npx cdk deploy --all and verify that the STAC API endpoint responds without the Lambda import error.

Written by the indexing model from the issue text.

Description

Deploying eoapi-template from a fresh clone produced a STAC API that returned 500 Internal Server Error on every request. The cause seemed to be dependency resolution: pyproject.toml specifies eoapi-cdk>=10.3.0,<12, and a fresh uv sync resolves to the lower bound, 10.3.0. The STAC API runtime bundled by eoapi-cdk 10.3.0 raises an ImportModuleError at Lambda handler import. Upgrading eoapi-cdk to 11.6.0 resolved it for me.

Environment:

  • Fresh clone of eoapi-template, deployed to AWS (us-west-2)
  • uv sync resolved eoapi-cdk==10.3.0 (confirmed in uv.lock)
  • Python 3.14.2, Node v24.13.0, deployed via npx cdk deploy --all

What happened:

Once deployed, I attempted to hit the STAC API endpoint:
Image

Looking in the CloudWatch logs I noticed:
Image

Forcing eoapi-cdk to the latest version resolved it. Upon redeploying, I was able to hit the endpoint:

Image
Dominant language
Python
Stars
5
Forks
2
Avg merge
18h 23m
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from developmentseed/eoapi-template

All issues in developmentseed/eoapi-template

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.