Skip to content

docs(ec2): document how to correctly make cross stack connection calls#18796

Merged
mergify[bot] merged 6 commits intoaws:masterfrom
corymhall:corymhall/docs-sg-connections
Mar 4, 2022
Merged

docs(ec2): document how to correctly make cross stack connection calls#18796
mergify[bot] merged 6 commits intoaws:masterfrom
corymhall:corymhall/docs-sg-connections

Conversation

@corymhall
Copy link
Copy Markdown
Contributor

This PR adds documentation on how to correctly make cross stack
connections. If the connection is not made in the correct stack it can
lead to cyclic reference.

fixes #5047


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

This PR adds documentation on how to correctly make cross stack
connections. If the connection is not made in the correct stack it can
lead to cyclic reference.

fixes #5047
@gitpod-io
Copy link
Copy Markdown

gitpod-io bot commented Feb 2, 2022

@github-actions github-actions bot added the @aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud label Feb 2, 2022
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Feb 2, 2022
@corymhall corymhall requested a review from a team February 2, 2022 20:44
Copy link
Copy Markdown
Contributor

@madeline-k madeline-k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is very helpful clarification! 😄 Just have one minor comment.


// Stack 2
const sg2 = new ec2.SecurityGroup(this, 'SG2', {
allowAllOutbound: false, // if this is `true` then no egress rule will be created
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The examples probably should not use the same scope for sg1 and sg2, because they are supposed to be in different stacks. I think this could be confusing.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Updated!

@corymhall corymhall requested a review from madeline-k February 28, 2022 17:58
@corymhall corymhall requested a review from a team March 4, 2022 14:23
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Mar 4, 2022

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 09556fa
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit de31f9f into aws:master Mar 4, 2022
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Mar 4, 2022

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

TheRealAmazonKendra pushed a commit to TheRealAmazonKendra/aws-cdk that referenced this pull request Mar 11, 2022
aws#18796)

This PR adds documentation on how to correctly make cross stack
connections. If the connection is not made in the correct stack it can
lead to cyclic reference.

fixes aws#5047


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

@aws-cdk/aws-ec2 Related to Amazon Elastic Compute Cloud contribution/core This is a PR that came from AWS.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: document how to get around cyclic deps created by connections calls

4 participants