acloudguru-resources / course-aws-certified-developer-associate Goto Github PK

@fayecloudguru During the cloud guru DVA-C01 session, the scripts attched with one bug found, makes the experiment fails:

in the Cognito_Commands.txt file: step 5, the highlight part below is considered as typo, need to remove to keep consistency of the Role name with rest of the guide.

--roles unauthenticated=arn:aws:iam::xxxxx:role/Cognito_DynamoPoolUnauthRole --output json

More backgroud:

Cognito Commands:

1. Using the CLI, create new identity pool, named DynamoPool, allow unauthenticated entities.
   **** (use ^ - Shift + 6 if you are a windows user, not ) ****

   aws cognito-identity create-identity-pool
   --identity-pool-name DynamoPool
   --allow-unauthenticated-identities
   --output json

2. Create an IAM role named Cognito_DynamoPoolUnauth.

aws iam create-role --role-name Cognito_DynamoPoolUnauth --assume-role-policy-document file://myCognitoPolicy.json --output json

3. Grant the Cognito_DynamoPoolUnauth role read access to DynamoDB by attaching a managed policy (AmazonDynamoDBReadOnlyAccess).

aws iam attach-role-policy --policy-arn arn:aws:iam::aws:policy/AmazonDynamoDBReadOnlyAccess --role-name Cognito_DynamoPoolUnauth

4. Get the IAM role Amazon Resource Name (ARN).
   aws iam get-role --role-name Cognito_DynamoPoolUnauth --output json

5. Add our role to the Cognito Identity Pool. Replace the pool ID with your own pool ID and use the role ARN from the previous step.

aws cognito-identity set-identity-pool-roles
--identity-pool-id "us-east-1:xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
--roles unauthenticated=arn:aws:iam::xxxxx:role/Cognito_DynamoPoolUnauthRole --output json

6. Double check it worked using:

aws cognito-identity get-identity-pool-roles --identity-pool-id "us-east-1:xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

7. We can now specify the Cognito credentials in our application - i.e. in the JavaScript section of our webpage!
   Replace the identity pool ID with your own and the role ARN with your own role ARN.
   We are going to add this snippet to our index.html:

AWS.config.credentials = new AWS.CognitoIdentityCredentials({
IdentityPoolId: "us-east-1:xxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
RoleArn: "arn:aws:iam::xxxxx:role/Cognito_DynamoPoolUnauthRole"
});

During Lab "Creating a Lambda Function Using the AWS Console", it is expected to create a Lambda function using the code creating-a-lambda-function-using-the-aws-console/index.js.

Currently Lambda defaults to Node.js 20.x, however the code supplied is for Node.js 16.x. I propose that a one line comment is added to the top of the code to state that it requires the Node 16.x runtime.

@michaelolear AWS has recently updated the default NodeJS runtime from v16 to v18 which enforces the uses of ESM imports. While the tutorial video shows the use of NodeJS v16, it would be great to have a NodeJS v18 compatible version and include a note in the video to specify which version the guru should use.

After typing this i
[ec2-user@ip-172-31-82-70 Create_A_DynamoDB_Table_Demo]$ aws dynamodb batch-write-item --request-items file://items.json
i got this error
An error occurred (ResourceNotFoundException) when calling the BatchWriteItem operation: Requested resource not found. when trying to create a table.

The following line in the Cognito demo command has a closing double quote that does not match the opening quote. The quotes are around the identity-pool-id argument.

Amazon Linux 2023 does not have mysql in yum by default, so the bootstrap.sh script does not work.

It needs to be updated to use the commands in this tutorial:
https://linux.how2shout.com/installing-mysql-8-server-client-on-amazon-linux-2023/