Week 3 Worklog

Solve the Hybrid DNS resolution challenge between On-premise and Cloud environments.
Implement Cross-VPC connectivity using VPC Peering.
Infrastructure troubleshooting and account stabilization.
Discuss project plans and programming language choices with the team.

Day	Task	Start Date	Completion Date	Reference Material
2	- Account Recovery: Resolved billing/payment method issues to ensure business continuity for the training environment.	09/21/2025	09/23/2025	REFER HERE
3	- Route 53 Resolver: + Inbound Endpoint: Enabling On-prem to resolve Cloud domains. + Outbound Endpoint: Enabling Cloud resources to resolve On-prem domains. - Executed DNS Forwarding labs.	09/24/2025	09/25/2025	REFER HERE
4	- VPC Peering Setup: + Established peering between two distinct VPCs. + Routing: Updated Route Tables in both VPCs to direct traffic via the Peering Connection (`pcx-xxx`). + Verified connectivity using private IPs.	09/25/2025	09/26/2025	REFER HERE
5	- Project Planning: Initial brainstorming session for the Capstone Project based on learned core services.	09/28/2025	09/28/2025

Successfully created a new AWS account with initial configurations, ensuring continued participation with the FCJ team.
Gained a solid understanding of Route 53 and Hybrid DNS configuration:
- Created and configured Outbound Endpoint for Route 53 Resolver.
- Set up Route 53 Resolver and Inbound Endpoints.
- Successfully connected to RD Gateway Server during practical exercises.

Mastered Route 53 Resolver architecture for complex Hybrid Cloud DNS scenarios.
Understood VPC Peering limitations:
- Non-transitive nature (VPC A <-> B <-> C does not imply A <-> C).
- Requirement for “DNS Resolution” enabling to resolve private hostnames.
Stabilized the sandbox environment for advanced networking labs.