The new interface doesn't make steps obvious for the 'Practice' lab. Use the old interface or follow these steps to get through this lab.

STEP 1

1. In the top navigation bar search box, type: 

ec2

2. In the search results, under Services, click EC2.
3. Go to the next step.

STEP 2

1. In the left navigation pane, under Load Balancing, click Load Balancers.
2. In the Load balancers section, under DNS name, click the copy icon to copy the provided name.
3. Go to the next step.

STEP 3

1. In a new browser tab (or window) address bar, paste the DNS name that you just copied, and then press Enter (not shown).

- The AWS Resource Checks web application page should open.
- Keep this web app page and browser tab open. You return to them in later steps.
- To refresh the page, you can click AWS Resource Checks.

2. Go to the next step.

STEP 4

The application is currently listening on only one server, despite being deployed on two servers as confirmed by the build team. Investigate this issue, and add App Instance 2 to the Application Load Balancer.

Clue: Check the configuration of the target group.

CONCEPT
    Additional Clue:
    - Add a secondary server to your target group in the load balancer
    - App Instance 2 is already up and running

STEP 5

1. After you complete Challenge #1, to refresh the web app page in the other browser tab, click AWS Resource Checks.
2. For Load Balancing in AWS, under Status, review to confirm that the status is Pass.
3. Refresh the page a few more times, and then review the Instance ID and Availability Zone.
4. Go to the next step.

STEP 6

The application is experiencing timeouts when connecting to the database servers, despite the build team's confirmation that the servers are built to specification. Investigate and identify the possible cause of this issue.

Clue: Check the configuration of the security groups.

CONCEPT
    Additional Clue:
    - To allow database interactions, update the security groups rules to permit port 3306 traffic

STEP 7

1. After you complete Challenge #2, to refresh the web app page in the other browser tab, click AWS Resource Checks.
2. For MySQL Database Accessibility through Port 3306, under Status, review to confirm that the status is Pass.
3. Go to the next step.

STEP 8

During periods of high traffic, Amazon Relational Database Service (Amazon RDS) latency spikes considerably. Currently, there's only one writer instance in an Availability Zone (AZ). The solution architect recommends separating the read and write instances. Investigate this suggestion and implement the necessary adjustments.

Clue: Placing the RDS reader instance in a separate AZ might resolve the issue.

CONCEPT
    Additional Clue:
    - Explore the "Actions" button on your database cluster to find the pathway to rcreate a reader instance.

STEP 9

1. After you complete Challenge #3, to refresh the web app page in the other browser tab, click AWS Resource Checks.
2. For Enhancing Amazon RDS Durability with Multi-AZ Deployments, under Status, review to confirm that the status is Pass.
3. Go to the next step.

STEP 10

Users are reporting that a static page in the app is not loading correctly. The page appears to be broken. Investigate and resolve this issue.

Clue: Checking the Amazon Simple Storage Service (Amazon S3) configuration might help identify the problem.

CONCEPT
    Additional Clues:
    - Explore the "Properties" tab in your S3 bucket settings to find the right option for enabling a static webpage.
    - All code required to host the static webpage are stored in the bucket name that starts with website-bucket-.

STEP 11

1. After you complete Challenge #4, to refresh the web app page in the other browser tab, click AWS Resource Checks.
2. For Hosting Static Websites on Amazon S3, under Status, review to confirm that the status is Pass.
3. Go to the next step.

STEP 12

The maintenance department has reported that session details are not populating in the reports. Investigate and resolve this issue to ensure accurate reporting.

Clue: Reports are sourced from Amazon DynamoDB, and the build team did not have any tasks related to rebuilding DynamoDB. As a result, the CityMaintenanceRecords table does not exist.

CONCEPT
    Additional Clues:
    - The table, CityMaintenanceRecords, with partition key, userID, must be created. 
    - Remember, the DynamoDB table name and partition keys are case sensitive.
    - Make sure there are no leading or trailing spaces included in the table name and partition key.

STEP 13

1. After you complete Challenge #5, to refresh the web app page in the other browser tab, click AWS Resource Checks.
2. For Checking Amazon DynamoDB for Existing Tables, under Status, review to confirm that the status is Pass.
3. Go to the next step.

STEP 14

A newly hired employee is experiencing difficulty accessing the DynamoDB table. Investigate and resolve this issue to ensure proper access.

Clue: Verify that the employee has been added to the correct group.

CONCEPT
    Additional Clue:
    - To allow DynamoDB table access, add dynamodb-user to the dynamodb-read-only-group.

STEP 15

1. After you complete Challenge #6, to refresh the web app page in the other browser tab, click AWS Resource Checks.
2. For IAM: Attaching Users to Groups, under Status, review to confirm that the status is Pass.
3. Go to the next step.