diff --git a/docs/ace-backbone/_images/backbone-tgw013.png b/docs/ace-backbone/_images/backbone-tgw013.png new file mode 100644 index 00000000..742a521a Binary files /dev/null and b/docs/ace-backbone/_images/backbone-tgw013.png differ diff --git a/docs/ace-backbone/_images/backbone-tgw014.png b/docs/ace-backbone/_images/backbone-tgw014.png new file mode 100644 index 00000000..f7d72a18 Binary files /dev/null and b/docs/ace-backbone/_images/backbone-tgw014.png differ diff --git a/docs/ace-backbone/_images/backbone-tgw015.png b/docs/ace-backbone/_images/backbone-tgw015.png new file mode 100644 index 00000000..80d2d7f7 Binary files /dev/null and b/docs/ace-backbone/_images/backbone-tgw015.png differ diff --git a/docs/ace-backbone/_images/backbone-tgw016.png b/docs/ace-backbone/_images/backbone-tgw016.png new file mode 100644 index 00000000..4af2835f Binary files /dev/null and b/docs/ace-backbone/_images/backbone-tgw016.png differ diff --git a/docs/ace-backbone/_images/backbone-tgw017.png b/docs/ace-backbone/_images/backbone-tgw017.png new file mode 100644 index 00000000..b2bc7c5f Binary files /dev/null and b/docs/ace-backbone/_images/backbone-tgw017.png differ diff --git a/docs/ace-backbone/_images/backbone-tgw018.png b/docs/ace-backbone/_images/backbone-tgw018.png new file mode 100644 index 00000000..a6b05185 Binary files /dev/null and b/docs/ace-backbone/_images/backbone-tgw018.png differ diff --git a/docs/ace-backbone/_sources/docs/backbone.md b/docs/ace-backbone/_sources/docs/backbone.md index 8270981e..6b93dbca 100644 --- a/docs/ace-backbone/_sources/docs/backbone.md +++ b/docs/ace-backbone/_sources/docs/backbone.md @@ -37,16 +37,8 @@ Initial Topology | **POD#** | **Copilot** | |:----------:|:---------------:| -| 1 | POD1 | -| 2 | POD2 | -| 3 | POD3 | -| 4 | POD4 | -| 5 | POD5 | -| 6 | POD6 | -| 7 | POD7 | -| 8 | POD8 | -| 9 | POD9 | -| 10 | POD10 | +| 1 | POD## | + | ## Access credentials @@ -59,7 +51,7 @@ student Password: ```bash -1012fw633#SYTY3 +############# ``` ## LAB Pre-Req @@ -167,7 +159,7 @@ It will take roughly **2 minutes** for the Aviatrix Controller to completing the ```{figure} images/backbone-tgw07.png --- -height: 250px +height: 600px align: center --- Attachment @@ -179,6 +171,7 @@ Let's continue building the cloud backbone, now you are asked to create the `Tra ```{figure} images/backbone-tgw08.png --- +height: 400px align: center --- Initial Topology for Task#3 @@ -218,6 +211,7 @@ Now it's time to deploy a pair of **`Transit GWs`** inside the VPC created on th ```{figure} images/backbone-tgw011.png --- +height: 400px align: center --- Inital Topology for Task #4 @@ -227,39 +221,114 @@ Go to **CoPilot > Cloud Fabric > Gateways > Transit Gateways** and click on the ```{figure} images/backbone-tgw12.png --- +height: 400px align: center --- Transit Gateways section ``` -### Deploy Aviatrix Spoke GW +Ensure these parameters are entered in the pop-up window `"Create Transit Gateway"`. + +- **Name:** transit-aws +- **Cloud:** AWS (Standard) +- **Account:** aws-account +- **Region:** us-east-1 (N. Virginia) +- **VPC/VNet:** transit-aws +- **Instance Size:** c6in.large +- **High Performance Encryption:** **ON** +- **Peer To Transit Gateways:** transit-azure + +then click on the `"+ Instance"` button! + +**Instance-1**: +- **Attach to Subnet:** us-east-1a + +**Instance-2**: +- **Attach to Subnet:** us-east-1b + +```{figure} images/backbone-tgw013.png +--- +align: center +--- +Transit GW Template +``` + +Do not forget to click on **SAVE**. + +```{note} +The Aviatrix Controller will deploy two Transit Gateways and, at the same time, it will establish the peering with the predeployed Transit Gateways in Azure. +``` + +```{caution} +The Aviatrix Controller will deploy two Transit Gateways and, at the same time, it will establish the peering with the predeployed Transit Gateways in Azure. +``` + +You can monitor the progress of the task! +Go to **CoPilot > Monitor > Notifications > Tasks** and expand the task named `"Create transit gateway: transit-aws"`. + +```{figure} images/backbone-tgw014.png +--- +height: 400px +align: center +--- +Task in progress +``` + +```{caution} +it will take roughly **10 minutes** for the Aviatrix Controller for completing this task, therefore, be patient! +``` -- The public IP address will be different (Public EIP automatically allocated by CSP) -- The Subnet CIDR could be different (automatically picked up by Aviatrix Controller) -- Region: us-east-1 +Now go to **CoPilot > Cloud Fabric > Topology**, click on `"Managed"` for hiding all the unmanaged VPCs (i.e. VPCs without an Aviatrix GW) and then click on the `"Collapse all VPC/VNets"` button. -![Spoke](images/egress_spoke_gw.png) +```{figure} images/backbone-tgw015.png +--- +height: 400px +align: center +--- +Dynamic Topology +``` -Check the Egress setting. The Egress traffic is going through the AWS NAT GW. +You will notice the presence of the newly created **peering**. -![Egress](images/egress_egress.png) +## Task #5: Attach Transit Gateway to aws-tgw -### Enable spoke GW to become the Egress GW +Now Let's attach the Transit GWs in AWS to the AWS TGW. -1. Click +Local Egress on VPC/VNets. -2. In the Add Local Egress on VPC/VNets dialog, select the VPC/VNets on which to enable Local Egress. -3. Click Add. +```{figure} images/backbone-tgw016.png +--- +height: 400px +align: center +--- +Initial Topology for task #5 +``` -[Read more at Aviatrix Documentation](https://docs.aviatrix.com/copilot/latest/network-security/index.html) +Go to **CoPilot > Networking > Connectivity > AWS TGW** and click on the `"Attach Transit Gateway"` button. -![Local](images/egress_add_local.png) +```{figure} images/backbone-tgw017.png +--- +align: center +--- +"Attach Transit GW" button +``` + +Ensure this parameter is entered in the pop-up window `"Attach Transigt Gateway to AWS-NVirginia-TGW"`. + +- **Transit Gateway:** transit-aws + +```{figure} images/backbone-tgw018.png +--- +align: center +--- +Attachment Template +``` -Add Local Egress on VPC/VNets -Adding Egress Control on VPC/VNet changes the default route on VPC/VNet to point to the Spoke Gateway and enables SNAT. Egress Control also requires additional resources on the Spoke Gateway.VPC/VNets +Do not forget to click on **SAVE**. -Now the diagram should look like the following: +```{caution} +it will take roughly **3 minutes** for the Aviatrix Controller for completing this task, therefore, be patient! +``` -![Vpc](images/egress_vpc.png) +## Task #6: Attach Transit Gateway to aws-tgw ## Conclusion diff --git a/docs/ace-backbone/docs/Requirements.html b/docs/ace-backbone/docs/Requirements.html index 3bc75f9c..a71c5093 100644 --- a/docs/ace-backbone/docs/Requirements.html +++ b/docs/ace-backbone/docs/Requirements.html @@ -324,7 +324,7 @@
1
2
3
4
5
6
7
8
9
10
|
+
1012fw633#SYTY3
+#############
@@ -513,7 +487,7 @@ Task #2: Attach VPC to AWS TGW
-
+
@@ -523,7 +497,7 @@ Task #2: Attach VPC to AWS TGW#
Let’s continue building the cloud backbone, now you are asked to create the Transit VPC
.
@@ -384,7 +384,7 @@ 2 - Dynamic Topology
-
+
The following topology will appear on your Copilot
@@ -394,14 +394,14 @@ 2 - Dynamic Topology
-
+
The following screen will appear:
Verify Backbone components are receiving the routes across Multicloud environment including Equinix.
@@ -508,7 +508,7 @@SSH from your laptop to the instance aws-instance, using your favourite SSH client:
@@ -525,7 +525,7 @@Access all the application instances/VMs using your laptop’s browser using the following links:
@@ -535,7 +535,7 @@Q7. For Data Plane Verification, how to find the public and private IP address of Instances deployed in CSP’s?
@@ -555,13 +555,13 @@Q9. Which Path is best for an application to communicate between AWS and GCP?
diff --git a/docs/ace-backbone/docs/quiz.html b/docs/ace-backbone/docs/quiz.html index fba6c40d..5fd5db5e 100644 --- a/docs/ace-backbone/docs/quiz.html +++ b/docs/ace-backbone/docs/quiz.html @@ -344,7 +344,7 @@