This topic describes how to get started with Elastic Container Instance.
Procedure in the Container Service console
Elastic Container Instance and Kubernetes are seamlessly connected to provide a hierarchical solution. In this solution, Elastic Container Instance schedules and manages underlying pods, while Kubernetes serves as a Platform as a Service (PaaS) layer on top of Elastic Container Instance to manage workloads. You can use one of the following methods to connect Elastic Container Instance to Kubernetes:
Run pods of Kubernetes clusters only on Elastic Container Instance
When you deploy a Serverless Kubernetes (ASK) cluster, the entire cluster runs on Elastic Container Instance. This eliminates the need to focus on operations and maintenance (O&M) and capacity issues of the underlying virtual machines (VMs).
Run pods of Kubernetes clusters on both Elastic Container Instance and traditional servers
You can connect Elastic Container Instance to Kubernetes clusters by deploying virtual nodes to improve the resource usage and elasticity of the clusters and reduce running costs.
For more information, see Connect Kubernetes to Elastic Container Instance.
If you know about Kubernetes or plan to deploy your business in Kubernetes, we recommend that you deploy and manage your business in Container Service for Kubernetes (ACK) or ASK clusters.
After you create ASK clusters in the Container Service console, you can deploy applications in the clusters. The pods generated when you deploy the applications have a one-to-one correspondence to elastic container instances. Perform the following steps:
After you create ACK clusters in the Container Service console, you must deploy virtual nodes in the clusters and then schedule applications to the virtual nodes. Pods on virtual nodes have a one-to-one correspondence to elastic container instances. Perform the following steps:
Procedure in the Elastic Container Instance console
If your business does not require features such as container orchestration, load balancing, timed scheduling, and auto scaling, or if you plan to use API operations to manage Elastic Container Instance resources, you can deploy containers by using the Elastic Container Instance console. Perform the following steps:
Activate services and grant required permissions.
If you are prompted for permissions when you log on to the Elastic Container Instance console, follow the on-screen instructions to activate Elastic Container Instance and Resource Access Management (RAM) and grant required permissions to related RAM roles. The permissions to be granted include the permissions on Elastic Compute Service and Virtual Private Cloud (VPC). For more information, see Authorize a RAM role.
Create an elastic container instance.
Before you create an elastic container instance, take note of the following items:
You must select a region and zone based on your business needs to create a VPC, vSwitch, and security group before you can create an elastic container instance.
If Internet access is required, you must associate a Network Address Translation (NAT) gateway or an elastic IP address (EIP) with the VPC in which the elastic container instance is located, or associate an EIP with the instance.
For more information, see the following topics:
Use the elastic container instance.
After an elastic container instance is created, you can view the events and logs of the instance and debug containers in the instance. For more information, see the following topics: