AWS Integration Lab Manual

Introduction

One of the most compelling reasons to adopt VMware Cloud on AWS is to integrate your existing systems which sit in your VMware Cloud environment, with application platforms which reside in your AWS Virtual Private Cloud (VPC) environment. The intergration which VMware and AWS have created allows for these services to communicate, for free, across a private network address space for services such as EC2 instances, which connect into subnets within a native AWS VPC, or with platform services which have the ability to connect to a VPC Endpoint, such as S3 Storage.

Understanding Integrations with AWS Services

aws-1

As the above diagram illustrates, the VMware stack not only sits next to the AWS services, but is tightly integrated with these services. This introduces a new way of thinking about how to design and leverage AWS services with your VMware SDDC. Some integrations our customers are using include:

  • VMware front-end and RDS backend
  • VMware back-end and EC2 front-end
  • AWS Application Load Balancer (ELBv2) with VMware front-end (pointing to private IPs)
  • Lambda, Simple Queueing Service (SQS), Simple Notification Service (SNS), S3, Route53, and Cognito
  • AWS Lex, and Alexa with the VMware Cloud APIs

These are only a few of the integrations we’ve seen. There are many different services that can be integrated into your environment. In this exercise we’ll be exploring integrations with both AWS Simple Storage Service (S3) and AWS Relational Database Service (RDS).

Note: There is a requirement in this lab to have completed the steps in the Working with your SDDC Lab concerning Content Library creation, Network creation, and Firewall Rule creation.

How these integrations are possible

In addition to sitting within the AWS Infrastructure, there is an Elastic Network Interface (ENI) connecting VMware Cloud on AWS and the customer’s Virtual Private Cloud (VPC), providing a high-bandwidth, low latency connection between the VPC and the SDDC. This is where the traffic flows between the two technologies (VMware and AWS). There are no EGRESS charges across the ENI within the same Availability Zone and there are firewalls on both ends of this connection for security purposes.

How is traffic secured across the ENI?

aws-2

From the VMware side (see image below), the ENI comes into the SDDC at the Compute Gateway (NSX Edge). This means, on this end of the technology we allow and disallow traffic from the ENI with NSX Firewall rules. By default, no ENI traffic can enter the SDDC. Think of this as a security gate blocking traffic to and from AWS Services on the ENI until the rules are modified.

aws-3

On the AWS Services side (see image below), Security Groups are utilized. For those who are not familiar with Security Groups, they act as a virtual firewall for different services (VPCs, Databases, EC2 Instances, etc). This should be configured to deny traffic to and from the VMware SDDC unless otherwise configured.

aws-4

In this exercise, everything has been configured on the AWS side for you. You will however walk through how to open AWS traffic to come in and out of your VMware Cloud on AWS SDDC.

Compute Gateway Firewall Rules for Native AWS Services

aws-5

  1. In the VMware Cloud on AWS portal click the Networking & Security tab
  2. Click Groups in the left pane
  3. Click ADD GROUP

Name Workload Group

aws-6

  1. Type PhotoAppVM for the Name
  2. Leave Virtual Machine select for Member Type
  3. Click Set VMs under Members

Select VMs - Workload Group

aws-7

  1. Click to select Webserver01
  2. Click SAVE

Save Group - Workload Group

aws-8

  1. Click SAVE

Firewall Rules

aws-9

  1. Click Networking & Security tab in your VMware Cloud on AWS Portal
  2. Click Gateway Firewall in the left pane
  3. Click and select Compute Gateway
  4. Click ADD NEW RULE

Add New Rule - AWS Inbound

aws-10

  1. Name your new rule AWS Inbound
  2. Click on Set Source

Select Source - AWS Inbound

aws-11

  1. Click to select Connected VPC Prefixes
  2. Click SAVE

Set Destination - AWS Inbound

aws-12

  1. Click on Set Destination

Select Destination - AWS Inbound (Continued)

aws-13

  1. Click to select PhotoAppVM
  2. Click SAVE

Set Service - AWS Inbound

aws-14

  1. Click on Set Service

Set Service - AWS Inbound (Continued)

aws-15

  1. Click to select Any
  2. Click SAVE

Publish - AWS Inbound

aws-16

  1. Click on PUBLISH

Note: Make sure to leave All Uplinks in the Applied To section.

Add New Rule - AWS Outbound

aws-17

  1. Click ADD NEW RULE
  2. Name your new rule AWS Outbound
  3. Click on Set Source

Select Source - AWS Outbound

aws-18

  1. Click to Select PhotoAppVM
  2. Click SAVE

Set Destination - AWS Outbound

aws-19

  1. Click on Set Destination

Select Destination - AWS Outbound

aws-20

  1. Click to select Connected VPC Prefixes
  2. Click SAVE

Set Service - AWS Outbound

aws-21

  1. Click on Set Service

Set Service - AWS Outbound (Continued)

aws-22

  1. Under Select Services type 3306
  2. Select MySQL checkbox
  3. Click SAVE

Publish - AWS Outbound

aws-23

  1. Click PUBLISH

Note: Make sure to leave All Uplinks in the Applied To section.

Add New Rule - Public In

aws-23a

  1. Click on ADD NEW RULE

Add New Rule - Public In (Continued)

aws-24

  1. Type Public In for Name
  2. Click on Set Source

Select Source - Public In

aws-25

  1. Click to select Any
  2. Click SAVE

Set Destination - Public In

aws-26

  1. Click on Set Destination

Select Destination - Public In

aws-27

  1. Click to select PhotoAppVM
  2. Click SAVE

Set Service - Public In

aws-28

  1. Click Set Service

Set Service - Public In (Continued)

aws-29

  1. Type HTTP 80 under Select Services
  2. Click to Select HTTP
  3. Click SAVE

Publish - Public In

aws-30

  1. Click PUBLISH

Note: Make sure to leave All Uplinks in the Applied To section.

AWS Relational Database Service (RDS) Integration

Amazon RDS makes it easy to set up, operate, and scale a relational database in the cloud. It provides cost- efficient and resizable capacity while automating time-consuming administration tasks such as hardware provisioning, database setup, patching and backups. It frees you to focus on your applications so you can give them the fast performance, high availability, security and compatibility they need.

In this exercise, you will be able to integrate a VMware Cloud on AWS virtual machine to work in conjunction with a relational database running in Amazon Web Services (AWS) that has been previously setup on your behalf.

Make Note of Webserver01 IP Address

aws-31

You will be using the VM created in the previous module in order to complete this exercise.

  1. In your vCenter interface for VMware Cloud on AWS, find your Webserver01 VM you deployed, and ensure it has been assigned an IP address as shown in the graphic.

Assign Public IP

aws-32

  1. Go back your VMware Cloud on AWS portal and click on the Networking & Security tab in order to request a Public IP address
  2. Click Public IPs in the left pane
  3. Click on REQUEST NEW IP
  4. In the notes area type PhotoAppIP
  5. Click SAVE

Note New Public IP

aws-33

Take note of your newly created Public IP.

Create a NAT Rule

aws-34

  1. Click NAT in the left pane
  2. Click ADD NAT RULE
  3. Type PhotoApp NAT for Name
  4. Ensure the Public IP you requested in the previous step appears under Public IP
  5. Leave All Traffic (no change)
  6. Type the IP address of your Webserver01 VM you noted at the beginning of this exercise
  7. Click SAVE

AWS Relational Database Service (RDS) Integration Exercise

aws-35

On your browser, open a new tab and go to: https://vmcworkshop.signin.aws.amazon.com/console

  1. Account ID or alias - Please refer to the information on the card provided to you for Account ID information
  2. IAM user name - Student# (where # is the number assigned to you)
  3. Password - VMCworkshop1211
  4. Click Sign In

Please note you might get either of the 2 sign on screens above. If you get the one on the right, enter Account ID and click Next

RDS Information

aws-36

  1. You are now signed in to the AWS console. Make sure the region selected is Oregon
  2. Click on the RDS service (You may need to expand All services)

RDS Instance

aws-37

  1. In the left pane click on Databases
  2. Click on the RDS instance that corresponds to designated number

Note: Be aware that you may need to look on Page 2 of this view to find your DB

aws-38

  1. Scroll down to the Details area and under Connectivity & security notice that the RDS instance is not publicly accessible, meaning this instance can only be accessed from within AWS
  2. Click in the blue hyperlink under Security groups

Security Groups

aws-39

  1. Choose the Student##-RDS-Inbound RDS Security group corresponding to you (may not match your student number)
  2. After highlighting the appropriate security group click on the Inbound tab below

Note: VMware Cloud on AWS establishes routing in the default VPC Security Group, only RDS can leverage this or create its own

Outbound Traffic

aws-40

  1. Click Outbound tab
  2. You can see All traffic (internal to AWS) allowed, this includes your VMware Cloud on AWS SDDC logical networks.

Elastic Network Interface (ENI)

aws-41

AWS Relational Database Service (RDS), also creates its own Elastic Network Interface (ENI) for access which is separate from the ENI created by VMware Cloud on AWS.

  1. Click on Services to go back to the Main Console
  2. Click on EC2

ENI (Continued)

aws-42

  1. In the EC2 Dashboard click Network Interfaces in the left panel
  2. All Student environments belong to the same AWS account, therefore, hundreds of ENI’s may exist. In order to minimize the view type RDS in the search area and press Enter to add a filter
  3. Highlight your Student##-RDS-Inbound security group corresponding to your student number based on the second octect of the CIDR block in the last column.

    In this example the CIDR block is 172.6.8.187, this would correspond to student 6

  4. Make note of the Primary private IPv4 IP address for the next step

Photo App

aws-41

  1. On your smart phone (tablet or personal computer), open up a browser and type your public IP address you requested in the VMware Cloud on AWS portal in the browser address bar followed by /Lychee (case sensitive) ie: 1.2.3.4/Lychee
  2. Enter the database connection information below (case sensitive), using the IP address you noted in the previous step from the RDS ENI:

    Database Host: x.x.x.x:3306 Database Username: student# (where # is the number assigned to you) Database Password: VMware1!

  3. Click Connect

Enter Login Information

aws-42

  1. Type student# (where # is the number assigned to you) for user name and VMware1! for password.
  2. Click Sign In

Photo Albums

aws-43

Congratulations, you have successfully logged in to the photo app!

OPTIONAL: Feel free to take a picture of the room with your smart phone and upload it to the Public folder.

In summary, the front end (web server) is running in VMware Cloud on AWS as a VM, the back end which is a MySQL database is running in AWS Relational Database Service (RDS) and communicating through the Elastic Network Interface (ENI) that gets established upon the creation of the SDDC.

You have completed the AWS Integraton Lab.

Updated:

Leave a Comment