aws / aws/chalice

Chalice deployments within VPCs in multiple accounts

Open
#1,407 4 comments 0 reactions 0 assignees View on GitHub
feature-request
Dominant language
Python
Stars
11.1k
Forks
1k
Avg merge
1d 22h
Merged PRs (30d)
2

Description

Hi. I have a usecase where I want to deploy my chalice app in different accounts and different regions within an account.
For one account / region, specifying subnet-ids and security-group ids works great but hardcoding these values in a multi-account / multi-region setup isn't scalable at all.

Looking for suggestion / attempted solutions, workarounds if somebody has experienced this issue already.

Thanks.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Begin by tracing how Chalice handles subnet and security-group IDs for VPC deployments, then compare the configuration needs across accounts and regions. The issue has no concrete acceptance criteria, so a defined approach and validation plan would be needed before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.