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
Currently there's no way to use roles as AWS authentication method which is needed for more automatable clusters so this feature would be great for large deployments on that platform since you can then have a static slave/node IAM image that is in an autoscalable group and not need to post-configure the key or have it pre-baked in the image.
AC:
Flocker can be configured to use IAM roles for AWS authentication/authorization
The text was updated successfully, but these errors were encountered:
@sgnn7 thank you for the feedback! I will bring this to our product team.
Could you elaborate on your use case a big more so we can gather a little detail on the usage of such a feature? E.g. is this specific to using flocker with the amazon EBS backend?
@wallnerryan The use case like you guessed is Flocker with EBS backend.
What we want to do is have an autoscaling group that has the least amount of configuration post-AMI creation so that we only need the control-service location for Flocker which can be a DNS entry so it can be fully automated and permissions handled through our instance roles vs users (i.e. permissions are determined in AWS by the launched instance type).
Currently there's no way to use roles as AWS authentication method which is needed for more automatable clusters so this feature would be great for large deployments on that platform since you can then have a static slave/node IAM image that is in an autoscalable group and not need to post-configure the key or have it pre-baked in the image.
AC:
The text was updated successfully, but these errors were encountered: