~/.hadean/deployment/init
directory.~/.hadean/deployment/init/readme.md
and can be viewed either as raw text, or with a markdown renderer.az
CLI installed. Then, simply open PowerShell and run the script provided, specifying a location.az login --identity
, and use managed service identity to create and destroy dynamic resources.aws
CLI installed. Then, simply create a new stack from our template:HadeanPlatformClusterRole
which clusters will use for their permissions. The policy in this role is tightly constrained to the specific permissions that the platform uses.HadeanPlatformClusterProfile
which has the role we just created assigned to it.HadeanPlatformClusterUserPolicy
which when assigned to a user gives them the ability to associate the instance profile with an EC2 instance and pass its role to that instance.HadeanPlatformClusterUserPolicy
policy to the groups or users that are going to use the platform. This will give those users the ability to use the instance profile to setup the credentials for the scheduler, so that it can dynamically scale.GetHostedZone
, GetHostedZoneCount
, GetHostedZoneLimit
, ListHostedZones
, ListHostedZonesByName
, ListHostedZonesByVPC
.ChangeResourceRecordSets
, GetChange
, ListResourceRecordSets
.Resource
part of the policy, by setting it to the ARN of the hosted zone you created.--domain-name
argument to the hadean cluster create
command, specifying the name used by the hosted zone. For example, if you've registered hadean.com.
, then your users must use --domain-name hadean.com
when creating clusters.