C3_W2_Assignment - Glue credential is not working

Before you post, please make sure to:

  1. Receiving an error on credentials There was a problem loading the file ‘credentials’. Details:
    [Errno 2] No such file or directory: ‘/shared/submission/credentials’

  2. Add all required tags in the tag option (top-right of the post):

    • dl-ai-learning- navigates to Coursera-platform

    • AWS Data Engineering –> Course 3 Data Storage and Queries –> Week 2 –> Programming Assignment: Assignment 2: Building a Data Lakehouse with AWS Lake Formation and Apache Iceberg

  3. Description - When executed some python scripts received error as credentials are not provided. here was a problem loading the file ‘credentials’. Details:
    [Errno 2] No such file or directory: ‘/shared/submission/credentials’

reading IAM Role (yes): couldn’t find resource

│ with module.landing_etl.data.aws_iam_role.glue_role,
│ on modules/landing_etl/iam_roles.tf line 1, in data “aws_iam_role” “glue_role”:
│ 1: data “aws_iam_role” “glue_role” {



│ Error: no matching EC2 Subnet found

│ with module.landing_etl.data.aws_subnet.public_a,
│ on modules/landing_etl/network.tf line 1, in data “aws_subnet” “public_a”:
│ 1: data “aws_subnet” “public_a” {



│ Error: reading EC2 Security Group: operation error EC2: DescribeSecurityGroups, https response error StatusCode: 400, RequestID: f0f46b85-4049-463d-b5c2-0d565b61a743, api error InvalidGroupId.Malformed: Invalid id: “yes” (expecting “sg-…”)

│ with module.landing_etl.data.aws_security_group.db_sg,
│ on modules/landing_etl/network.tf line 5, in data “aws_security_group” “db_sg”:
│ 5: data “aws_security_group” “db_sg” {

Note: Screenshots are welcome, but please do not post full assignment code.

Hi @Rupam17
Are you still having trouble with AWS credentials? Sometimes restarting the lab helps.

Hi @Rupam17 I’m a bit confused with your issue. The [Errno 2] No such file or directory: ‘/shared/submission/credentials’ looks like a grader error, am I correct? However the terminal prints you add below look more like issues when running the lab. For these, I suggest restarting the lab. If you share your lab id (you can find it by clicking on the question mark button on the top bar) I can restart your AWS resources so you get a clean start. Also, please make sure you completed all the steps in the lab, so that everything is correctly configured