github.com/emc-advanced-dev/unik@v0.0.0-20190717152701-a58d3e8e33b7/docs/providers/aws.md (about)

     1  # AWS UniK Provider
     2  
     3  UniK supports running rumprun and OSv unikernels on AWS.
     4  The AWS stub of your `daemon-config.yaml` file should look something like the following:
     5  ```yaml
     6  providers:
     7    #...
     8    aws:
     9      - name: aws-1
    10        region: us-west-1
    11        zone: us-west-1a
    12  ```
    13  UniK requires that your AWS credentials are set via [default AWS environment variables](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-environment) or your [AWS config file](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-config-files).
    14  
    15  UniK stores AWS data in the following paths:
    16  * JSON representation of the state: `$HOME/.unik/aws/state.json`
    17  
    18  * UniK boot volumes are stored as AMIs
    19  * UniK data volumes are stored as EBS Backed Volumes
    20  * UniK instances are `m1.small` EC2 Instances
    21  
    22  If UniK gets into a bad state (i.e. you manually remove a file or AWS VM), you should manually edit the `$HOME/.unik/aws/state.json` file to remove the instance that no longer exists. UniK will eventually become self-correcting to deal with disruptions in the state.