Skip to content

fix: add AWS_ROLE_ARN and AWS_REGION for dstack-ingress STS (CPL-152) #190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Garandor merged 1 commit into from
Mar 26, 2026
Merged

fix: add AWS_ROLE_ARN and AWS_REGION for dstack-ingress STS (CPL-152) #190

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/workflows/deploy-phala.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,9 @@
# ${DOCKER_IMAGE}-lit-api-server
# ${DOCKER_IMAGE}-otel-collector
# DOCKERHUB_USERNAME - Docker Hub username
# CERTBOT_AWS_ACCESS_KEY_ID - Route 53 IAM access key for DNS-01 challenge
# CERTBOT_AWS_ROLE_ARN - IAM role ARN for STS assumption (required by dstack-ingress)
# CERTBOT_AWS_REGION - AWS region for STS endpoint (e.g. "us-east-1")

name: Deploy to Phala CVM

Expand Down Expand Up @@ -156,6 +159,8 @@ jobs:
-e "s|\${CERTBOT_DOMAIN}|${DOMAIN}|g" \
-e "s|\${CERTBOT_AWS_ACCESS_KEY_ID}|${{ vars.CERTBOT_AWS_ACCESS_KEY_ID }}|g" \
-e "s|\${CERTBOT_AWS_SECRET_ACCESS_KEY}|${{ secrets.CERTBOT_AWS_SECRET_ACCESS_KEY }}|g" \
-e "s|\${CERTBOT_AWS_ROLE_ARN}|${{ vars.CERTBOT_AWS_ROLE_ARN }}|g" \
-e "s|\${CERTBOT_AWS_REGION}|${{ vars.CERTBOT_AWS_REGION }}|g" \
docker-compose.phala.yml > docker-compose.deploy.yml
cat docker-compose.deploy.yml

Expand Down
13 changes: 8 additions & 5 deletions docker-compose.phala.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,10 @@
# GCP_SERVICE_ACCOUNT_JSON - GCP service account key (raw JSON or base64-encoded)
# GCP_PROJECT_ID - GCP project ID (e.g. "my-gcp-project")
# CERTBOT_DOMAIN - Custom domain for TLS (e.g. "api.chipotle.litprotocol.com")
# CERTBOT_AWS_ACCESS_KEY_ID - Route 53 IAM credentials for DNS-01 challenge
# CERTBOT_AWS_SECRET_ACCESS_KEY - Route 53 IAM credentials for DNS-01 challenge
# CERTBOT_AWS_ACCESS_KEY_ID - Route 53 IAM access key for DNS-01 challenge
# CERTBOT_AWS_SECRET_ACCESS_KEY - Route 53 IAM secret key for DNS-01 challenge
# CERTBOT_AWS_ROLE_ARN - IAM role ARN for STS assumption (required by dstack-ingress)
# CERTBOT_AWS_REGION - AWS region for STS endpoint (e.g. "us-east-1")

# RUST_LOG filter shared by lit-actions and lit-api-server.
# App code stays at trace; per-module overrides suppress low-value internals:
Expand Down Expand Up @@ -114,9 +116,10 @@ services:
SET_CAA: "true"
AWS_ACCESS_KEY_ID: "${CERTBOT_AWS_ACCESS_KEY_ID}"
AWS_SECRET_ACCESS_KEY: "${CERTBOT_AWS_SECRET_ACCESS_KEY}"
# Optional: for STS role assumption instead of direct IAM keys
# AWS_ROLE_ARN: "${CERTBOT_AWS_ROLE_ARN}"
# AWS_REGION: "${CERTBOT_AWS_REGION}"
# STS role assumption — required by dstack-ingress for Route 53 access.
# The IAM user (AWS_ACCESS_KEY_ID) assumes this role to modify DNS records.
AWS_ROLE_ARN: "${CERTBOT_AWS_ROLE_ARN}"
AWS_REGION: "${CERTBOT_AWS_REGION}"
volumes:
- /var/run/dstack.sock:/var/run/dstack.sock
- cert-data:/etc/letsencrypt
Expand Down