This article contains a list of the most common problems users encounter when using our hands-on labs and some ideas for working around those issues.
I can't access all the resources the lab requires
Often this problem occurs because the system has not completed configuration yet when you started working on the lab. Wait 5-10 minutes to let the cloud provider create all required resources and try again.
I can't connect to the EC2 instance
If you get the connection timed out error, you might have a corporate firewall or a network limitation. If you have another network available, you can try that. Also, some software in your personal computer could limit your sessions as well. You could try disabling that software or using a different computer.
If you get the connection refused error, your security group may not have finished filtering the requests. Wait 5-10 minutes and try again.
I'm having issues while creating resources
Issues while creating resources such as IAM group, IAM user, and DB Cluster are often due to errors in the naming. Due to our strict policy, the resources in most labs must be named exactly as described in the instructions. Note that names are case sensitive.
My lab session was terminated
The system automatically terminates lab sessions and blocks the account when it detects an unauthorized operation. You account can also be blocked if you exceed the lab quota.
If this the first time your account was blocked, the system automatically unblocks it after 2 hours. If this is not the first time, you should contact customer support.
For further information about limitation on hands-on labs, see the following articles: