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 May 10, 2024. It is now read-only.
The documentation for the user_data of the run_instances method is
user_data (string) – The Base64-encoded MIME user data to be made available to the instance(s) in this reservation.
It might be true for python scripts, but for shell scripts, it seems passing raw shell scripts works, while passing base64-encoded shell scripts doesn't work.
Thanks,
The text was updated successfully, but these errors were encountered:
I noticed the same issue with boto (2.32.1) botocore (0.56.0)
With run_instances() base64-encoded string does not work but raw string works.
The documentation for run_instances() and run() asks for Base64 user_data.
The documentation for request_spot_instances() does not specify any encoding for user_data.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On page:
http://boto.readthedocs.org/en/latest/ref/ec2.html
The documentation for the user_data of the run_instances method is
user_data (string) – The Base64-encoded MIME user data to be made available to the instance(s) in this reservation.
It might be true for python scripts, but for shell scripts, it seems passing raw shell scripts works, while passing base64-encoded shell scripts doesn't work.
Thanks,
The text was updated successfully, but these errors were encountered: