Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add docs with networking scenarios

未关闭
#116 2 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
半天
新手友好度
44/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
aws, postgresql

调研方向

未指定文档文件或入口点。检查仓库现有的文档结构,添加两个网络场景及其安全性、成本和连接性说明,并验证示例对于执行部署的用户来说清晰且准确。

由索引模型根据 Issue 内容生成。

描述

While working on #114 I have experimented with different networking arrangements and have been reminded that it is easy to create a configuration that does not work! It could be helpful for users to see a few example configurations while they consider their own deployment.

Here are a few that do work:

Scenario 1: Higher security, higher cost

  • RDS Instance in a PRIVATE_ISOLATED subnet
    • [optional] pgbouncer instance in a PRIVATE_WITH_EGRESS subnet
    • pgstac_secret host value is the private IP address for pgbouncer or the RDS hostname
  • Lambdas added to the vpc in a PRIVATE_WITH_EGRESS subnet (adds a NAT Gateway which costs $)
    • granted connect access to either the RDS instance or the pgbouncer instance
  • important: add an S3 Endpoint to the vpc to make it possible to read data from S3 buckets in the same region as the VPC for free even within the vpc instead of paying the NAT Gateway tax

Scenario 2: Lower security, lower cost

  • RDS Instance in a PUBLIC subnet
    • [optional]pgbouncer instance in a PUBLIC subnet with a public IP address assigned
    • pgstac_secret host value is the public IP address for the pgbouncer instance or the RDS hostname
    • important: RDS Instance (or pgbouncer instance) allow all traffic (any Ipv4) on port 5432
  • Lambdas in PUBLIC subnet
  • Makes it possible to connect to the database from any client with the credentials
    • convenient for loading STAC items without the ingestor infrastructure
主要语言
Python
星标
29
派生
6
平均合并
9 小时 27 分钟
30 天内合并 PR
2

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

developmentseed/eoapi-cdk 的其他 Issue

查看 developmentseed/eoapi-cdk 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。