Create an environment

Mon, 01 Jan 0001 00:00:00 +0000

An environment is a named group of stacks and clusters , such as production or staging. Every stack belongs to one.

Post the name of the environment:

curl -X POST "https://api.webscale.com/v2/environments" \
 -H "Authorization: Bearer <my-access-key>" \
 -H "Content-Type: application/json" \
 -d '{"name": "Production"}'

{
 "href": "/v2/environments/3ps666yxcanq",
 "name": "Production",
 "keyword": "production"
}

A stack takes that whole href in its environment field. See Create an EKS stack for an example.

Webscale builds the keyword from the name unless you send your own, as the response above shows. Stacks put it into the names and tags of the resources they create.

Create an EKS stack

Mon, 01 Jan 0001 00:00:00 +0000

Follow these steps to create an EKS stack and prepare it for Helm deployments.

Prerequisites

Access key: An access key for the account, created in the Access keys section of your Profile page. See Webscale service users for a key that belongs to automation.
AWS provider: An AWS provider in the account. See Working with Providers .
Environment: An environment to hold the stack. See Create an environment .
Network: Subnet IDs when you bring a network you already have. A new network does not need them. See Network topology .
Name: A name for the stack, which becomes the name of the EKS cluster. It must be unique within the environment and among the stacks that share your AWS account. Use 3 to 30 characters from a-z, 0-9, and -, starting with a lowercase letter or a digit.

Every request goes to https://api.webscale.com and carries the access key:

How-Tos on Webscale Product Documentation

Create an environment

Create an EKS stack

Prerequisites