Skip to content
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

Jump to bottom

Separate higher-level constructs into their own module #2570

Closed
SoManyHs opened this issue May 17, 2019 · 3 comments
Closed

Separate higher-level constructs into their own module #2570

SoManyHs opened this issue May 17, 2019 · 3 comments
Assignees
@SoManyHs
Labels
feature-request A feature should be added or improved.

Comments

@SoManyHs
Copy link
Contributor

Based on #2402 (comment), we may want to move higher-level constructs ("L3s", or constructs that incorporate components from multiple AWS services, into its own module.
@SoManyHs SoManyHs added the feature-request A feature should be added or improved. label May 17, 2019
@SoManyHs SoManyHs self-assigned this May 17, 2019
@SoManyHs
Copy link
Contributor Author

Per offline discussion with @eladb, working on writing a doc to elaborate on this idea

@eladb
Copy link
Contributor

eladb commented May 21, 2019

Thanks! Looking forward

@MrArnoldPalmer
Copy link
Contributor

This was resolved by creation of the aws-ecs-patterns module. See the design pr for info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SoManyHs SoManyHs

Labels
feature-request A feature should be added or improved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@eladb @MrArnoldPalmer @SoManyHs