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
To avoid any issues that may arise with failed tag application - either due to a subsequent failure of the tags call, or because of the (albeit small) time between API calls - the tags should be assigned in the same API call as the cluster creation.
The text was updated successfully, but these errors were encountered:
mgmarino
added a commit
to mgmarino/mrjob
that referenced
this issue
Mar 31, 2021
AWS has deprecated several managed EMR policies (see here) and the replacement policies make use of tags for authorization.
Currently, tags are assigned after a cluster is made, in a separate api call, though the underlying boto3 client supports setting tags on cluster creation.
To avoid any issues that may arise with failed tag application - either due to a subsequent failure of the tags call, or because of the (albeit small) time between API calls - the tags should be assigned in the same API call as the cluster creation.
The text was updated successfully, but these errors were encountered: