Hello,
I have an issue with : Week 2 Assignment:
Building a Data Lakehouse with AWS Lake Formation and Apache Iceberg,to sta
the lab workbench refuse to start, can you help me please?
Tank you Amir
Hi @lazeni.F , just checking in to see if you were able to retry the lab. My records show that our engineer has refreshed the lab for you. Let me know if you have any questions about this.
Thank you for your message, everything is ok now
@Amir_Zare et al.,
I am having some strange behaviour while running the
source scripts/setup_jupyter_env.sh it is persistently showing the WARNING:
A newer release of “Amazon Linux” is available.
bash: export: `vpc-0197325212618c4fb’: not a valid identifier
I am unable to do anything at all.
Hello @amiguel
Looks like the bash is not able to locate your VPC. The problem is probably stemming from choosing a wrong VPC upon creation of the Cloud9 environment. Please, make sure that you choose all the correct settings for your Cloud9 environment.
I’m facing the same issue. Not able to solve this even after refreshing.
My Cloud 9 environment have two VPC options even after I deleted the envirnment I created
I’m getting two VPC options and tried with both options resulting in
error
“WARNING:A newer release of “Amazon Linux” is available.
bash: export: `vpc-0a65748b1e012a4a3’: not a valid identifier”
I did the following
- deleted the environment and created new. Still this two options comes up
- stopped. removed the cache and stop the lab and restarted - still see the same two options
what to do next?
Hello @siljith
The warning about newer release of Amazon Linux is non-blocking. I get this too but the execution of the command continues without a problem.
It is strange that you are getting two VPCs with the name of
de-c3w2a1. If you continue to have this problem even after a fresh lab restart and you are sure that you are selecting all the correct options when creating the Cloud9 environment, please fill out the lab refresh form to see if that helps.
hi @Amir_Zare ,
I waited for 2 hrs to get the time run out and then initiated the aws & cloud 9
it worked.
thanks
@Amir_Zare et al.,
I have successfully set up my VPC, but I’m still experiencing issues with some accounts. Despite re-establishing the connection, I’m unable to deploy Glue Jobs. I’m currently following section 4.3 of the deployment guide, but I’m consistently encountering errors.
Appreciate any help, as I am stuck on this for almost 96 hours per se.
Hello @amiguel
You are getting the missing metadata error. This means that the glue jobs that you are trying to run have not been created. Have you followed step 4.3.3?
You should run
terraform init and terraform apply after you uncomment the transform module sections in the main.tf and outputs.tf file. This will create the transform glue jobs that you need to run.
Hello @Amir_Zare,
I’m still struggling to resolve the issue despite trying to follow the previous instruction. Unfortunately, I’ve encountered another problem that has been persisting for 48 hours now. Every time I try to start the Lab, it takes an excessively long time to load and ultimately crashes with the following error message:
Hello again @amiguel
Unfortunately, there is a problem with Vocareum that has affected many students. I have reported this, and our team are communicating with Vocareum to solve this. Thank you for your patience.