Q: You need two VPCs in different AWS accounts to communicate privately. How do you set this up?
Option 1: VPC Peering
Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In a previous role, our monitoring paged me for a similar incident across our AWS VPC infrastructure. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
Option 1: VPC Peering
- Create a peering connection between the two VPCs (cross-account supported).
- Accept the peering request in the other account.
- Update route tables in both VPCs to point to each other's CIDR via the peering connection.
- Update Security Groups to allow traffic from the other VPC's CIDR.
- Central hub. Connect all VPCs (and on-prem) to TGW.
- Fully transitive. Any connected VPC can reach any other.
Remediation & Permanent Safeguards
Limitation: Not transitive. If VPC A peers with B, and B peers with C, A can't talk to C through B. Option 2: AWS Transit Gateway Option 3: AWS PrivateLink
- Better for many VPCs. Costs more than peering.
- Expose a specific service (not the whole VPC) across accounts.
- The consumer VPC creates an Interface Endpoint pointing to the provider's endpoint service.
- Traffic stays on AWS backbone.
- Create a peering connection between the two VPCs (cross-account supported).
- Accept the peering request in the other account.
- Update route tables in both VPCs to point to each other's CIDR via the peering connection.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Purging compromised IAM user credentials immediately prior to querying CloudTrail forensic event logs when configuring need VPCs different Deactivating a compromised key prevents abuse while preserving identity records for CloudTrail forensic queries to assess blast radius.
- Conflating local IAM Permissions Boundaries with organizational Service Control Policies (SCPs) when configuring need VPCs different SCPs define maximum permission guards at the AWS Organization level across accounts, whereas permission boundaries limit delegate privileges within a single account.
- Deploying single-AZ cloud infrastructure for production workloads without multi-AZ failover resilience when configuring need VPCs different Availability Zone hardware failures or localized network partitions cause complete service downtime when resources are not distributed across >=2 AZs.
- Jumping straight to SSH or instance restarts without reviewing CloudWatch metrics and AWS Systems Manager logs when configuring need VPCs different Senior SREs triage control plane and hypervisor metrics via CloudWatch and SSM Session Manager before executing invasive host-level actions.