Follow the steps in this section to create a cloud Infrastructure and deploy and expose your application to the web using the DuploCloud Portal.

Using the user ID and URL provided by the workshop instructor, log in to the DuploCloud Portal using SSO with either Microsoft or Google.

Navigate to Kubernetes -> Services -> Add Service. The Add Service page displays.

• Name: nginx

• Docker image: nginx:latest (this is a sample public image)

Click Next, and then click Create.

To create a Tenant, navigate to Administrator -> Tenants -> Add. The Create a Tenant pane displays.

• Name: dev[YOUR_INITIALS]01 (For example, devab01)

• Plan: non-prod (Specifying the Plan associates the new Tenant with the Infrastructure you created earlier)

Click Create.

This may take around 2 minutes. You may see a generated fault in Administrator -> Faults or the exclamation (!) icon displayed in the top right during provisioning.

Once it’s ready, select your new Tenant using the Tenant drop-down list box at the top of the screen.

To create an EKS Worker Node, navigate to Cloud Services -> Hosts -> Add. The Add Host page displays.

Friendly Name: host01

After clicking Add, wait until the Status displays Running and Fleet displays Connected.

Navigate to Kubernetes -> Services and select the nginxService from the list.

Click Load Balancers -> Configure Load Balancer. The Add Load Balancer Listener pane displays.

• Type: Application LB

• Container port: 80

• External port: 443

• Visibility: Public

• Application mode: Docker Mode

• Health check: /

• Backend protocol: HTTP

• Certificates: WILDCARD.test04-apps.duplocloud.net

Click Add and wait until the Service is Running and the Load Balancer displays a status of Ready.

Enable HTTP to HTTPs Redirect

Navigate to Kubernetes -> Services and select the nginxService.

Click Load Balancers. On the Other Settings card, click Edit. Enable the HTTP to HTTPS redirect option.

You can find the created DNS Name displayed on this page, CNAME'd to your Load Balancer name. Copy and paste the URL in the DNS Name card into your browser address to verify your application is available with a Status of Running. It may take a few minutes for the application to start.

Creating the Alert

Navigate to Observability -> Alerts -> Add. The Create Alert pane displays.

• Resource Type: EC2

• Resource: [select a previously created EC2 instance]

Click Next to proceed with defining metrics data.

Defining metrics data

After clicking Next, continue defining the metrics data:

• Metric Name: CPUUtilization

• Statistic: Average

• Operator: >=

• Threshold: 75

• Period: 5 Minutes

• Severity: Critical

Click Create.

Set the Alarm with a Third-Party Integration

Navigate to Observability -> Faults -> Update Notifications Config. The Set Alert Notifications Config pane displays.

If instructed, enter additional data and click Update to set the alarm.

Navigate to Cloud Services -> Storage -> S3 and click Add. The Create an S3 Bucket pane displays.

Enter a Name for your S3 Bucket and click Create.

Once your bucket is created, select the S3 Bucket to open the Details page. From this page, click the Console button.

This opens the AWS S3 console using Just-In-Time (JIT) credentials, allowing you to work with the bucket in AWS.

Navigate to Cloud Services -> Database -> RDS -> Add. The Create a RDS page displays.

• Name: [add -demo to the name DuploCloud pre-populates]

• RDS Engine Version: MySQL 8.0.39

• RDS instance size: db.t3.small

• User name: demo

• User password: W5i6Uv6LQtyApVyJDrAq

Click Create.

In the DuploCloud Portal, navigate to Administrator -> Infrastructure -> Add and enter the following details:

• Name: non-prod

• Region: us-west-2

• VPC CIDR: 10.221.0.0/16

• Subnet CIDR Mask: 24

• Availability Zones: 2

• Select the Enable EKS option

This takes about 20 minutes. Once it’s ready, double-check that a DuploCloud Plan (Administrator -> Plans) has been created with the same name (non-prod).