"Create another IAM Policy and another IAM User." again, the policy json appears to be in the wrong place. Should probably name or tag all of these policies and users as well so they can be searched and deleted in the cleanup step. about live-labs HOT 1 CLOSED

confluentinc commented on September 24, 2024

"Create another IAM Policy and another IAM User." again, the policy json appears to be in the wrong place. Should probably name or tag all of these policies and users as well so they can be searched and deleted in the cleanup step.

from live-labs.

Comments (1)

mkananizadeh commented on September 24, 2024

Thanks, I added more clarification and moved the policy config to the right place.

from live-labs.

Related Issues (16)

Review of DynamoDB, Redshift, S3 live lab HOT 1
You should mention here that the AWS account needs root level permissions
The steps should use consistent language. I'd suggest a lower level header (###) for each:
I'd suggest some stronger language HOT 2
They will also need to create a separate schema registry API key, right? HOT 1
This diagram looks ok, but to take it to the next level, it should be remade in Figma with the updated icons. The icons used are from old branding.
Should use svg rather than png. PNG files don't scale well for different screens.
The text should be bigger. In figma, you can use a standard 1920x1080 frame with standard text styles from the web dev library so the font size will be more appropriate
"Create an IAM Policy and attach it to an IAM User." I am not following along the lab as I read, but this seems like not enough information. Which user? Which policy? I think you should explicitly instruct us to create an IAM user called "confluent-s3-demo-user" or something like that. I then see the policy json after the next step. The policy json should be under this step, not the "Create a key pair for the IAM User you just created" step. HOT 1
"For DynamoDB you can either reuse the IAM User from S3 or create a new one." Too many choices. Be more explicit. "Create another IAM user called confluent-dynamo-demo-user" or some such. HOT 1
I would keep in mind to update this whenever ksqlDB gets Connect integration. You would then be able to create the connector with a ksqlDB query. HOT 1
I'd call this section before step 1 "Step 0: Create Accounts and Test Connectivity"
The port quiz step is confusing. At first it sounds like I need my machine to allow access to 443 and 9092 to the public internet. But then I see the "outbound traffic". Maybe simplify to "Test that your network allows outbound requests from your machine to ports 443 and 9092 over the public internet."
Streamline with Terraform HOT 1
Provide a lab workspace to run applications

"Create another IAM Policy and another IAM User." again, the policy json appears to be in the wrong place. Should probably name or tag all of these policies and users as well so they can be searched and deleted in the cleanup step. about live-labs HOT 1 CLOSED

Comments (1)

Related Issues (16)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent