cloudquest lab Role data analytics

You're encountering a common issue in AWS Cloud Quest labs where the permissions are restricted for security reasons. The error you're seeing with your Glue job trying to connect to OpenSearch suggests that there's indeed a permissions issue with the "AWSGlueServiceRole-lab" role not having proper access to the OpenSearch service.

In Cloud Quest lab environments, users typically cannot modify the pre-configured permissions, which is why you're unable to edit the role. This type of issue can occur due to:

1. A mismatch between the lab instructions and the current AWS console experience
2. The lab environment not being properly configured with all necessary permissions
3. A bug in the lab environment setup

To resolve this issue, you have a few options:

1. Restart the lab completely (not just repeating the steps) as this might reset any underlying configuration issues
2. Double-check that you're following all instructions exactly as provided, as Cloud Quest often uses specific naming conventions or pre-configured resources
3. Contact the AWS training team for support at: https://support.aws.amazon.com/#/contacts/aws-training

The AWS training team is the appropriate contact for Cloud Quest lab issues, as they can investigate and potentially fix permission problems in the lab environment. When contacting them, be sure to provide details about the specific lab ("Document Indexing and Search" in the Data Analytics role), the error message you're receiving, and the steps you've already taken.

Also, if you're accessing the lab through a URL, make sure you're in the correct AWS region. Some users have reported that Cloud Quest labs default to eu-north-1 when logging in, while many labs are designed to run in us-east-1, which can cause permission errors.
Sources
Cloud Quest Data Analytics "Securing the Data Lake" Issue | AWS re:Post
iam create user access error on cloud quest | AWS re:Post
CloudQuest - Database in practice step - permissions issue | AWS re:Post

From my end, Glue job ran successfully without any issue. Kindly ensure that the Glue version, Job parameters and Dependent JARs path are correct as per lab.