Usually, AWS CodeBuild can not access the VPC resources. To support access, you must provide additional VPC-specific configuration information as part of CodeBuild project configuration. This includes the VPC ID, VPC VPC subnet ID and security group ID. VPC build support then can access resources within the VPC.
VPC connection constructed from AWS CodeBuild make the following possible:
-
Integrated test run on the data private subnet isolated Amazon RDS database through your building.
-
Amazon ElastiCache directly query the data in the cluster pass the test.
-
And hosted on Amazon EC2, internal Web service interactions on Amazon ECS or internal use Elastic Load Balancing service.
-
From self-hosted internal project repository (such as for Python PyPI, for Java Maven for Node.js and npm) to retrieve dependencies.
-
Amazon S3 bucket access configured to allow access only by Amazon VPC terminal node object.
-
Elastic IP addresses through NAT gateways or NAT instance with your child gateway associated with the query requires a fixed IP address of the external Web service.
You can build your VPC to access any resource hosted.
Typically, resources in an VPC are not accessible by AWS CodeBuild. To enable access, you must provide additional VPC-specific configuration information as part of your CodeBuild project configuration. This includes the VPC ID, the VPC subnet IDs, and the VPC security group IDs. VPC-enabled builds are then able to access resources inside your VPC.