Loading

Sorry

Your web browser doesn't support some required capabilities.

This interactive simulation works best with the latest version of Chrome, Firefox, or Safari.

Sorry

An error occurred. Please reload the page or report this error to:
hol-feedback@vmware.com

Sorry

Sorry

Unable to initialize the simulation player:

Please reload the page or report this error to:
hol-feedback@vmware.com

X
↩ Return to the lab
HOL-1906-03: vRealize Automation and AWS

This is an interactive demo

Drive it with your mouse, your finger, or just use the arrow keys.

Use Learn mode to learn the demo. The orange boxes show where to click.

Use Present mode to hide the orange boxes and notes.

Click a Shortcut to jump to a specific part of the demo.

X
Hide notes
Restore notes
Open notes window
Increase font size
Decrease font size

This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment. In this simulation, you can use the software interface as if you are interacting with a live environment.

The orange boxes show where to click, and the left and right arrow keys can also be used to move through the simulation in either direction.

In this simulation, vRealize Automation  has already been deployed and setup.  You will complete the configuration to integrate Amazon Web Services EC2, create fabric groups, assign reservations, publish a blueprint, request for a catalog item, and manage deployed items.

Connecting vRealize Automation to Amazon Web Services

  1. Click on the Infrastructure tab.
  2. Click on Endpoints.
  3. Click on Endpoints. This is where you will add an Amazon Web Services account. 
  4. Click on AWS-EC2 to review the configuration.
  5. Click on the X icon on the top that says Warning Compute resources for this endpoint have been data collected. Changing endpoint credentials after data collection can cause provisioning failures or related problems.
  6. Click on the Properties tab.
  7. Click on the Associations tab.
  8. Click on the Cancel button.

Configure Fabric Groups and Reservations

  1. Click on Fabric Groups on the left navigation bar.
  2. Click AWS Development
  3. Click on Edit option.
  4. Click the scroll bar to scroll down.
  5. Click the scroll bar under Compute Resources: to view a list of AWS Regions that we are allowed to provision into.
  6. Click on AWS-EC2-us-west-2 checkbox to select the AWS Region to provision into.
  7. Click the OK button.
  8. Click on Infrastructure on the left navigation bar.
  9. Click on Compute Resources
  10. Click on Compute Resources
  11. Click on AWS-EC2-us-west-2 compute resources.
  12. Click on Edit option to review some basic settings of AWS-EC2-us-west-2.
  13. Click OK button.
  14. Click on AWS-EC2-us-west-2 compute resources.
  15. Click the New Reservation option.
  16. Click on Name: field and type AWS Development Reservation
  17. Click on Business group: dropdown list and select Development
  18. Click on Reservation policy: dropdown list and select AWS-Dev
  19. Click on Priority: field and type 1
  20. Click on Resources tab.
  21. Click on Assign to a subnet in a VPC checkbox.
  22. Click on vpc-ed5db989 checkbox.
  23. Click on subnet-0c24cd68 (172.16.30.0/24 us-west-2a) checkbox under Subnets:.
  24. Click on subnet-2b24cd4f (172.16.20.0/24 us-west-2a) checkbox under Subnets:.
  25. Click on subnet-5824cd3c (172.16.10.0/24 us-west-2a) checkbox under Subnets:.
  26. Click on default checkbox under Security groups:
  27. Click on Dev-DBServer checkbox under Security groups:
  28. Click on Dev-WebServer checkbox under Security groups:
  29. Click on the Save button.
  30. Click on Properties tab.
  31. Click on Alerts tab.
  32. Click on the OK button.
  33. Click on Infrastructure on the left navigation bar.
  34. Click on Reservations
  35. Click on Reservations
  36. Click on AWS Development Reservat... to review the reservations that was just created.
  37. Click on Resources tab.
  38. Click on Properties tab.
  39. Click on Alerts tab.
  40. Click on the Cancel button.
  41. Click on Infrastructure on the left navigation bar.

Creating and Publishing a Blueprint

  1. Click on Design tab on the top navigation bar.
  2. Click on the 2Tie-Wordpress-AWS blueprint to review details of the blueprint.
  3. Click the front-end component.
  4. Click on Reservation policy: dropdown list and select AWS-Dev option.
  5. Click on the Build Information tab to review machine specifications.
  6. Click the scroll bar to review all instance types that are available for front-end component.
  7. Click on the Machine Resources tab to review minumum and maximum configuration details.
  8. Click on Properties tab.
  9. Click the back-end component.
  10. Click on Reservation policy: dropdown list and select AWS-Dev option.
  11. Click on the Build Information tab to review machine specifications.
  12. Click on the Machine Resources tab to review minumum and maximum configuration details.
  13. Click on Properties tab.
  14. Click the Finish button to save the blueprint.
  15. Click on the X icon on the top that says Success Your blueprint is saved in draft state. You must publish your blueprint before it can be reused or placed in a catalog service
  16. Click on the Publish option to publish the blueprint to catalog service.
  17. Click on the X icon on the top that says Success Selected items were successfully published

Catalog Management and Entitlements

  1. Click on the Administration tab on the top navigation bar.
  2. Click on Catalog Management option on the left navigation bar
  3. Click on Catalog Items option on the left navigation bar.
  4. Click on 2Tier-Wordpress-AWS catalog item.
  5. Click the scroll bar to scroll to the bottom of the screen, which shows you the details of the catalog item.
  6. Click on Entitlements on the left navigation bar.
  7. Click on Development Serv... entitlement.
  8. Click on Items & Approvals tab.
  9. Click on 2Tier-Wordpress-AWS checkbox option.
  10. Click the OK button.
  11. Click the Finish button.
  12. Click on Logout on the top right.
  13. Click on Go back to login page button.

Requesting and managing a Catalog Item

  1. Click on username and type devuser
  2. Click on password and type VMware1!
  3. Click the Sign in button.
  4. Click the Catalog tab.
  5. Click on Amazon Web Services on the left navigation bar.
  6. Click on Request button.
  7. Click on front-end component on the left.
  8. Click on Instance type: dropdown list and select t2 - Micro Instance
  9. Click on Provision into: dropdown list and select Subnet in a VPC
  10. Click on Storage tab.
  11. Click on Network tab.
  12. Click on Subnet: dropdown list and select subnet-5824cd3c
  13. Click on Dev-WebServer checkbox under Security groups:
  14. Click on back-end component on the left.
  15. Click on Instance type: dropdown list and select t2 - Micro Instance
  16. Click on Provision into: dropdown list and select Subnet in a VPC
  17. Click on Storage tab.
  18. Click on Network tab.
  19. Click on Subnet: dropdown list and select subnet-2b24cd4f
  20. Click on Dev-DBServer checkbox under Security groups:
  21. Click on the Submit button.
  22. Click on the OK button.
  23. Click on Requests tab on the top navigation bar. You will see that the deployment has been completed successfully.
  24. Click on Request 32 to review details of the deployment.
  25. Click on Execution Information to review details of deployment execution.
  26. Click on the OK button.
  27. Click on EC2 Management Console browser tab.
  28. Click on Instances on the left navigation bar.
  29. Click on the AWSDev-004 checkbox to review instances details.
  30. Click on the AWSDev-004 checkbox again to uncheck.
  31. Click on the AWSDev-005 checkbox to review instances detail
  32. Click on vRealize Automation browser tab.
  33. Click on Items tab on the top navigation bar.
  34. Click on 2Tier-Wordpress-AWS- deployment to expand its provisioned items. Let’s try to access the wordpress application based on the IP Address of the front-end.
  35. Click on the square icon to open a new browser tab.
  36. Click on the browser address bar to load the web page. You will see a wordpress landing page.
  37. Click on scroll bar to navigate around the wordpress page
  38. Click on vRealize Automation browser tab.
  39. Click on the AWSDev-004 item to review instance details from vRealize Automation.
  40. Click on Storage tab.
  41. Click on Network tab.
  42. Click on Shutdown on the right navigation bar under Actions:
  43. Click on Execution tab.
  44. Click on the Submit button.
  45. Click on the OK button.
  46. Click on the Close button.
  47. Click on Requests tab on the top navigation bar. You will see that the Shutdown task has been completed successfully.
  48. Click on Request 33.
  49. Click the OK button.
  50. Click on Items tab on the top navigation bar.
  51. Click on 2Tier-Wordpress-AWS- deployment to expand on the provisioned items. 
  52. Click on AWSDev-004 to review changes made. You will see that the Status of the instance is Off.
  53. Click on EC2 Management Console browser tab.
  54. Click on the AWSDev-004 checkbox to review instances details. You will notice that the Instance State is stopped.
  55. Click on User’s Blog! - Just another wordpress blog browser tab.
  56. Click on the browser refresh icon. You will notice that the wordpress site is down.
  57. Click on the X icon to close the browser tab.
  58. Click on vRealize Automation browser tab.
  59. Click on the Close button.
  60. Click on 2Tier-Wordpress-AWS- deployment. 
  61. Click on Actions .
  62. Click on Destroy option.
  63. Click on front-end icon on the left navigation bar.
  64. Click on Delete Volumes: dropdown list and select Yes
  65. Click on back-end icon on the left navigation bar.
  66. Click on Delete Volumes: dropdown list and select Yes
  67. Click on the Submit button.
  68. Click on the OK button.
  69. Click on Requests tab on the top navigation bar. You will see that the Destroy task has been completed successfully.
  70. Click on Request 34 to review details of the request.
  71. Click on Execution Information to review details of deployment execution.
  72. Click on the OK button.
  73. Click on Items tab on the top navigation bar. The 2Tier-Wordpress-AWS deployment has been removed.
  74. Click on EC2 Management Console browser tab.
  75. Click on the AWSDev-004 checkbox to review instances details. You will notice that the Instance State is terminated.
  76. Click on the AWSDev-005 checkbox to review instances details. You will notice that the Instance State is terminated.
  77. Click on vRealize Automation browser tab.
  78. Click on Logout at the top right.
  79. Click on the Go back to login page button to end the lab.

This completes the simulation on vRealize Automation and Amazon Web Services integration.

To return to the lab, click the link in the top right corner or close this browser tab.

Copyright © 2018 VMware, Inc. All rights reserved.