Amazon Virtual Private Clouds (Amazon VPCs) are virtual networks that provide extra security to your application by isolating it from the public internet. By connecting to an Amazon VPC, users can securely run workflow actions and create Dev Environments linked to your VPC in CodeCatalyst. You can set a default VPC connection for a space, so that all workflow runs and Dev Environments will run connected to that VPC.
A VPC connection is a CodeCatalyst resource which contains all of the configurations needed for your workflow to access a VPC. Space administrators can add their own VPC connections in the Amazon CodeCatalyst console on behalf of space members. By adding a VPC connection, space members can run workflow actions and create Dev Environments that adhere to network rules and can access resources in the associated VPC.
For more information about setting up a VPC, see the Amazon VPC User Guide.
Considerations for administering VPC connections
-
You must have the Space administrator role or Power user role to manage VPC connections at the space level.
-
Project administrators can associate a VPC connection to their environment and Contributors can associate that VPC-connected environment with a workflow. When administering VPC connections as a Space administrator, you are maintaining these resources on behalf of space members.
Topics
Use cases
VPC connectivity from CodeCatalyst actions makes it possible to:
-
Run a workflow action that follows the network rules of a VPC connection.
-
Run a workflow action that accesses resources running in a VPC.
-
Deploy an update to an Amazon EKS cluster running in a VPC.
How do I get started with VPC connections?
The high-level steps to add and use a VPC connection are as follows:
-
In the AWS Management Console, create an Amazon Virtual Private Cloud (VPC) or use an existing VPC. A VPC is a virtual network that provides extra security to your application by isolating it from the public internet and allows you to securely run your workflow actions in CodeCatalyst. In order for your VPC to work with CodeCatalyst, it must have a certain configuration. For more information, see Amazon VPC setup requirements.
-
In your CodeCatalyst space settings, create a VPC connection. A VPC connection is a CodeCatalyst resource which contains all of the configurations needed for a workflow to access a VPC. For more information, see Adding VPC connections for a space.
-
Associate this VPC connection with an environment to use with your workflow actions. For more information, see Associating a VPC connection with an environment in the CodeCatalyst User Guide.
-
Within a workflow, associate the VPC-connected environment to your workflow action. When an action is configured with an environment that has a VPC connection, the action will run connected to the VPC, adhere to the network rules, and access resources specified by the associated VPC. For more information, see Associating an environment, account connection, and IAM role with a workflow action in the CodeCatalyst User Guide.
-
Create a Dev Environment associated to your VPC connection. For more information, see Creating a Dev Environment in the CodeCatalyst User Guide.
Limitations of VPC connections in CodeCatalyst
-
CodeCatalyst only supports creating VPC connections in the same region. For more information on the available regions, see CodeCatalyst VPC endpoint service names.
-
CodeCatalyst does not support VPC connectivity with the Lambda compute type. Instead, use the Amazon EC2 compute type.
-
CodeCatalyst does not support VPC connectivity with Windows. Instead, use Linux.
-
VPC connectivity may lead to longer action run times.
