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

L2 Constructs for Lattice Service #501

Closed
2 of 11 tasks
mrpackethead opened this issue May 7, 2023 · 2 comments
Closed
2 of 11 tasks

L2 Constructs for Lattice Service #501

mrpackethead opened this issue May 7, 2023 · 2 comments
Labels
l2-request request for new L2 construct management/tracking

Comments

@mrpackethead
Copy link
Contributor

mrpackethead commented May 7, 2023 •
edited

Description

A set of constructs, with methods for using the Lattice service with VPC.. The intial scope of these should be enough so that it is possible to implement environments that are detailed in the AWS Lattice Reference Architectures

It is envisaged that constructs would be created for; ( not an exclusive list

a service network,
a service, which will have 'targets' and listeners and rules
a method to associate a VPC with a service network
policys

Roles

Role User
Proposed by @mrpackethead
Author(s) @mrpackethead
API Bar Raiser @TheRealAmazonKendra
Stakeholders @NetDevAutomate

See RFC Process for details

Workflow

  • Tracking issue created (label: status/proposed)
  • API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
  • Kick off meeting
  • RFC pull request submitted (label: status/review)
  • Community reach out (via Slack and/or Twitter)
  • API signed-off (label api-approved applied to pull request)
  • Final comments period (label: status/final-comments-period)
  • Approved and merged (label: status/approved)
  • Execution plan submitted (label: status/planning)
  • Plan approved and merged (label: status/implementing)
  • Implementation complete (label: status/done)

Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.
@mrpackethead mrpackethead mentioned this issue May 7, 2023
Open
2 tasks
@mrpackethead
Copy link
Contributor Author

https://github.com/raindancers/latticeplay/tree/main/lib/applicationConstructs

@NetDevAutomate NetDevAutomate mentioned this issue May 18, 2023
Closed
11 tasks
@evgenyka evgenyka added the l2-request request for new L2 construct label Oct 11, 2023
@mrgrain mrgrain removed the status/proposed Newly proposed RFC label Nov 1, 2023
@mrgrain
Copy link
Contributor

mrgrain commented Nov 1, 2023

Duplicate of #502

@mrgrain mrgrain marked this as a duplicate of #502 Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
l2-request request for new L2 construct management/tracking
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mrgrain @mrpackethead @evgenyka