Prerequisites

Always review Items' documentation to learn about their specific prerequisites and dependencies.

For hands-on users wishing to deploy, make sure you have covered the basics:

Access Credentials: Ensure that you have any of the keys, secrets or tokens required by the Item
Local Prerequisites: Install any tooling needed for deployment, which for instance depending in the item can be:
- Ansible via pypi.org
- Terraform from hashicorp.com
- Helm from helm.sh
- ewccli via pypi.org

Item Deployment Best-Practices

There are many good practices you can follow to save yourself or your team the effort of dealing with avoidable security risks or downtime (see Best practices for tenancy management). When it comes to Item deployment specifically, we recommend to at least ensure the following:

Versioning: Always pin Item versions, for stability, to reduce the blast radius of bugs mistakenly introduce as part of new Item releases and facilitate rollbacks.
Secret management: Use environment variables or secret managers to temporarily make credentials available for deployment tools.

Deployment Guides

Depending on the item, a first deployment could include the steps to gain access to commonly needed credentials: SSH keys, OpenStack application credentials, Kubeconfig files, etc. You will find instructions as part of each Item's usage documentation.

Beyond the point of authorization, deployment steps are mainly dependent on the Item Technology. For detailed guidance per specific technology, you can get started with these examples:

By Technology

Ansible Playbook

Run Ansible Playbooks from your local or remote working environment, and configure existing compute instances (read more).

Terraform Module

Learn how to initialize, plan, and apply Terraform modules for provisioning and managing the state of EWC infrastructure (read more).

Deploying via ewccli

Learn how to use the ewccli python package to deploy items in your EWC tenancy (learn more).