Skip to content

Clarify AWS PrivateLink procedures for SaaS on AWS#6006

Open
bhavikbhavsar wants to merge 1 commit into
aap-clouds-latestfrom
docs/privatelink-procedure-clarity
Open

Clarify AWS PrivateLink procedures for SaaS on AWS#6006
bhavikbhavsar wants to merge 1 commit into
aap-clouds-latestfrom
docs/privatelink-procedure-clarity

Conversation

@bhavikbhavsar

Copy link
Copy Markdown

Summary

  • Reorder ingress PrivateLink steps so the support ticket is submitted before AWS VPC Endpoint creation.
  • Reorder egress PrivateLink steps (create Endpoint Service → submit ticket → approve connection → configure DNS) and expand split-horizon DNS guidance.
  • Add a note to inbound traffic control clarifying that Public Internet and PrivateLink access can coexist.
  • Add a PrivateLink traffic flow summary table mapping ingress/egress to PULL/PUSH connectivity models.

Test plan

  • Built Private Link chapter locally with asciidoctor assembly-saas-private-link.adoc
  • Review rendered HTML for step order, table formatting, and NOTE blocks
  • Confirm terminology aligns with PULL/PUSH models chapter

Made with Cursor

Reorder support-ticket and AWS console steps, document split-horizon DNS requirements, explain public vs PrivateLink coexistence, and add a traffic flow summary with PULL/PUSH mapping.

Co-authored-by: Cursor <cursoragent@cursor.com>

@LuuOW LuuOW left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Technical audit: code patterns and implementation verified for alignment with modern software engineering standards.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants