You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugThis issue is a bug.effort/smallSmall work item – less than a day of effortp2
Describe the bug
https://cdkworkshop.com/15-prerequisites/200-account.html#administrator-user
Administrator User Instructions to set up Programmatic Access are out-of-date with the new AWS Console experience.
Expected Behavior
Create the IAM user first, then after creation choose from several access key options.
Current Behavior
Go to the AWS IAM console and create a new user.
Type a name for your user (e.g. cdk-workshop) and choose “Programmatic access”.
Reproduction Steps
https://cdkworkshop.com/15-prerequisites/200-account.html#administrator-user
Possible Solution
Modify instructions to match the new console experience:
Create the IAM user first, then after creation choose from several access key options.
Additional Information/Context
No response
CDK CLI Version
No response
Section
prerequisites 200-account.html administrator-user
Browser
Chrome
Language
All
The text was updated successfully, but these errors were encountered: