-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ec2 run-instance incorrect description for --user-data #366
Comments
Please fix this and/or specify how to indicate that the data is base64 encoded. This just bit me as well. |
The data does not have to be base64-encoded. You can just supply any data and AWS CLI will do the encoding for you before sending to EC2. The bug is in the documentation, not the code. |
Yes, I know, I base64 encoded the data in accordance with the docs and then checked my instance and was confused. I was later further confused because it seems like the file: syntax was accepted before and now it's file://. |
Seems like this is still a problem here
|
I am using aws cli 1.0. Clearly the doc is incorrect.
whatever is specified after --user-data is passed straight. If I encoded base64, they show base64 encoded on the server metadata as well . So if I wanted to pass a file, I had to do the folllowing in order to get it to work
--user-data file:///path/to/the/file
It would be nice also to add an example to it
The text was updated successfully, but these errors were encountered: