Find here the most common issue encountered while doing our labs:
- Can't reach all the resources needed in the lab.
Commonly it's related to AWS. Wait a few (5-10) minutes to let the Cloud Provider create all resources needed.
- Can't connect to the EC2 instance.
"connection timed out": you might have a corporate firewall or a network limitation. Try the Lab with another internet connection.
Some software in your personal computer could limit your sessions as well. If you can't disable them, please use another computer for a test.
"connection refused": most of the times user has to wait a few minutes to let the security group filtering the requests.
- Issues while creating resources such as IAM group, IAM user, DB Cluster, etc.
This is commonly due to some 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.
- Lab session terminated
An unauthorized operation has been detected and, therefore, your lab session has been terminated and your account blocked.
An unauthorized operation has been detected and, therefore, your lab session has been terminated and your account blocked.
You exceeded the lab quota so your account was blocked.
If it's the first ban, the account will be unbanned automatically after 2 hours.
For further information about labs limitation please check the following article: