Hey there, 2 things:
1: Starting over article, step 1 may be a typo?
In the "Starting Over" article, (which is super helpful, appreciate it!)
the first instruction is to run rm ~/.ssh/aws-key.pem
The key that is generated for me is actually aws-key-fast-ai.pem
Not sure if this is a typo, or the script got updated to make a different key file name, but my computer can't find the file ~/.ssh/aws-key.pem when trying to remove. This confused me for a while so just putting it here as an FYI, it was fixed by running
2. I have an issue with the key pair when running the script with my IAM user. I did give him Administrator access and programmer access (that was on the setup screen in AWS but not in the video)
This was fixed by configuring aws with my root access credentials, then running the script.
not sure why AWS doesn't complain when done with IAM credentials in the video, and I would love to know why.
Key Pair Does Not Exist Issue
The script claims the key pair aws-key-fast-ai doesn't exist, but running ls on the .ssh directory shows that it is indeed there. I'm stuck on the errors generated from running the script.
This problem only occurs when I try to run the script with the IAM user I created.
$ bash setup_p2.sh.1
Waiter InstanceRunning failed: Max attempts exceededling the RunInstances operation: The key pair 'aws-key-fast-ai' does not exist
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:meter) when calling the CreateTags operation: The request must contain the parameter resourceIdSet
Waiting for instance start...
aws <command> help
aws <command> <subcommand> help
aws: error: argument --instance-id: expected one argument
An error occurred (MissingParameter) when calling the RebootInstances operation: The request must contain the parameter InstancesSet
All done. Find all you need to connect in the fast-ai-commands.txt file and to remove the stack call fast-ai-remove.sh
Connect to your instance: ssh -i /home/joshua/.ssh/aws-key-fast-ai.pem ubuntu@None
The key pair shows up in ssh, so why is the script saying key pair doesn't exist?
$ cd .ssh