1. Click View Details on your Software Defined Data Center
2. Click the Network tab
   • This is the area within the VMware Cloud on AWS portal where the Firewall Rules are created.
3. Click the Scroll Bar
4. Click to expand Firewall Rules
5. Click ADD RULE
6. Click the Rule Name field and type "vCenter Access"
7. Click the Source field and type "Any"
8. Click  <Select Option> under Service
9. Click HTTPS (TCP 443)
10. Click the Save button

1. Click the Settings tab
2. Click Default vCenter User Account to expand
3. Click vSphere Client (HTML5) to expand
4. Click vCenter Server API Explorer to expand
5. Click Power CLI Connect to expand
6. Click the Scroll Bar
7. Click vCenter FQDN to expand
8. Click the Scroll Bar
9. Click the Copy button under Password
10. Click the URL under the vSphere Client (HTML5) area to open the vCenter Server interface
11. Click the User Name field box and type "cloudadmin@vmc.local"
12. Click the Password field box and press any key to copy the Password to login to vCenter Server
13. Click Login 
14. Click to expand the SDDC-Datacenter in the left pane
15. Click to expand Cluster-1
    • It's important to note that while customer have visibility to the entire cluster, including the management stack within VMware Cloud on AWS, as a consumer of the service, customers work on a limited access model when it comes to vCenter. VMware is responsible for the entire virtual layer while customers' responsibilities are limited to the Virtual Machines and Logical Networks created in the VMware Cloud on AWS environment.

Content libraries are container objects for VM templates, vApp templates, and other types of files like ISO images.

You can create a content library in the vSphere Web Client, and populate it with templates, which you can use to deploy virtual machines or vApps in your VMware Cloud on AWS environment or if you already have a Content Library in your on-premises data center, you can use the Content Library to import content into your SDDC.

1. Click Menu
2. Click Content Libraries
3. Click the "+" sign in your Content Library window to add a new Content Library
4. Click the Name field and type "My On Premises Content Library"
5. Click the Notes field box and type in notes
6. Click the Next button
7. Click the Radio Button next to Subscribed content library to select it
8. Click the Subscription URL field and press any key to paste the URL of the Content Library to subscribe to
9. Click the Check Box for Enable Authentication
10. Click the Password field and press any key to type out the password
11. Click the Scroll Bar to display the rest of the information
12. Click the Next button
13. Click the WorkloadDatastore to select the storage location
14. Click the Next button
15. Click the Finish button

1. Click the Menu button in the vSphere Client
2. Click Global Inventory Lists from the drop down menu
3. Click on Logical Networks in the left pane
4. Click on the + ADD button to create a Logical Network
5. Click the Name field and type "LN2" for the name of the Logical Network
6. Click the CIDR Block field and type "192.168.2.0/24"
7. Click the Default Gateway IP field and type "192.168.2.1"
8. Click on the Check Box to enable the DHCP field
9. Click the IP Range field and type "192.168.2.100-192.168.2.200"
10. Click the DNS Domain Name field and type "corp.local"
    
11. Click the OK button to create your logical network

1. Click the Menu button in the vSphere Client
2. Click Policies and Profiles from the drop down menu
3. Click on the + New button to add a new Linux Customization Spec
4. Click the Name field and type "MyLinuxSpec"
5. Click the Description field and type "This is my Linux Spec"
6. Click on the Radio Button for Linux in the Target Guest OS field
7. Click the Next button
8. Click on the Radio Button for Enter a name and type "MyLinuxVM"
9. Click on the Check Box for Append a numeric value
10. Click on the Domain Name field and type "corp.local"
11. Click the Next button
12. Click the Drop Down Box next to the Area field and select America
13. Click the Side Bar to scroll down
14. Click New York in the Location field to select the time zone
15. Click on the Radio Button for Local time in the Hardware clock set to field
16. Click the Next button
17. Click the Next button on the Network screen to leave the default selection
18. Click the Primary DNS server field and type "10.46.159.10"
19. Click the DNS Search Paths field type "corp.local"
20. Click the ADD button
21. Click the Next button
22. Click the Finish button

1. Click on the Menu button in the vSphere Client
2. Click on Content Libraries
3. Click on My On Premises ContentLibrary to select the Content Library created earlier in this simulation
4. Click the Templates tab
5. Click (right click) on the centos01-web template
6. Click New VM from This Template
7. Click the Virtual Machine Name field and type "VM2"
8. Click to expand the SDDC-Datatcenter
9. Click on Workloads to select it
10. Click the Next button
11. Click to expand Cluster-1
12. Click on Compute-ResourcePool to select it
13. Click the Next button
14. Click the Next button on the Review Details screen
15. Click the WorkloadDatatstore as the VM Storage Policy on the Select Storage screen
16. Click the Next button
17. Click the Drop Down Box under the Destination Network field to select the Logical Network you created previously
18. Click on LN2
19. Click the Next button
20. Click the Finish button

1. Click the Virtual Machine name VM2 under recent tasks
2. Click ACTIONS
3. Click Power
4. Click Power On
5. Click on the VM Screen to launch the Console
6. Click on the Browser Tab vSphere-VM2
7. Click ACTIONS
8. Click Power
9. Click Power Off
10. Click YES to Confirm Power Off

1. Click ACTIONS
2. Click Template
3. Click Convert to Template
4. Click YES to Confirm Convert