Setting Up TeamCity for Amazon EC2
TeamCity Amazon EC2 integration allows you to configure TeamCity with your Amazon account and then start and stop images with TeamCity agents on-demand based on the queued builds.
Integrations with other cloud solutions are available.
It is assumed that the machine images are preconfigured to start TeamCity agent on boot (see details below).
Once a cloud profile is configured in TeamCity with one or several images, TeamCity does a test start for all the new images to learn about the agents on them.
Once the agents are connected, TeamCity stores their parameters to be able to process the build configurations-to-agents compatibility correctly.
For each queued build, TeamCity first tries to start it on one of the regular, non-cloud agents. If there are no usual agents available, TeamCity finds a matching cloud image with a compatible agent and starts a new instance for the image. TeamCity ensures that the running instances limit configured in the cloud profile is not exceeded.
Once an agent is connected from a cloud instance started by TeamCity, it is automatically authorized (provided there are available agent licenses). After that, the agent is processed as a regular agent.
If running timeout is configured on the cloud profile and it is reached, the instance is terminated (or stopped, if an existing Amazon instance has been selected as an image source).
On the instance terminating/stopping, its disconnected agent is removed from the authorized agents list and is deleted from the system.
Understanding Amazon EC2 and ability to perform EC2 tasks is a prerequisite for configuring and using TeamCity Amazon EC2 integration.
Basic TeamCity EC2 setup involves:
preparing an Amazon EC2 image (AMI) with an installed TeamCity agent
configuring EC2 integration on TeamCity server
Make sure the server URL specified on the Administration | Global Settings page is correct since agents will use it to connect to the server, if a custom server URL is not specified in the cloud profile settings.
Required IAM permissions
TeamCity requires the following permissions for Amazon EC2 Resources:
To use spot instances, the following additional permissions are required:
To use spot fleets, the following additional permissions are required:
To launch an instance with the IAM Role (applicable to instances cloned from AMI-s only), the following additional permissions are required:
An example of custom IAM policy definition (allows all EC2 operations from a specified IP address):
See the section below for permissions to set IAM roles on an agent instance.
Preparing Image with Installed TeamCity Agent
Here are the requirements for an image that can be used for TeamCity cloud integration:
TeamCity agent should be correctly installed.
TeamCity agent should start on machine startup.
buildAgent.propertiescan be left as is. The
authorizationTokenproperties can be empty or set to any value; they are ignored when TeamCity starts the instance.
Provided these requirements are met, usual TeamCity agent installation and cloud-provider image bundling procedures are applicable.
If you need the connection between the server and the agent machine to be secure, you will need to set up the agent machine to establish a secure tunnel (for example, VPN) to the server on boot so that TeamCity agent receives data via the secure channel.
Recommended image (for example, Amazon AMI) preparation steps:
Choose one of the existing generic images.
Start the image.
- Configure the running instance:
- Install and configure a build agent:
Configure server name and agent name in
conf/buildAgent.properties— this is optional if the image will be started by TeamCity, but it is useful to test if the agent is configured correctly.
It usually makes sense to specify
conf/buildAgent.propertiesto use the non-system drive (
Install any additional software necessary for the builds on the machine.
Run the agent and check it is working OK and is compatible with all necessary build configurations, and so on.
Configure the system so that the agent is started on machine boot (and make sure TeamCity server is accessible on machine boot).
For Windows, see also Additional configuration for Windows agents
- Install and configure a build agent:
Test the setup by rebooting the machine and checking that the agent connects normally to the server.
- Prepare the Image for bundling:
Remove any temporary/history information in the system.
Stop the agent (under Windows stop the service but leave it in Automatic startup type)
Delete the content
tempdirectories in agent home (optional)
<Agent Home>/conf/amazon-*file (optional)
config/buildAgent.propertiesto remove properties:
serverUrlcan be removed for EC2 integration plugins. Other plugins might require that it is present and set to correct value.
Stop the running instance and make a new image from it (or just stop it if an existing Amazon instance has been selected as an image source).
Additional configuration for Windows agents
To ensure proper TeamCity agent communication with EC2 API (including access to additional drives) on Windows, add a dependency from the TeamCity Build Agent service on the AmazonSSMAgent or EC2Launch/EC2Config service (the service which ensures the machine is fully initialized in regard to AWS infrastructure use). This can be done, for example, via the Registry or using sc config (for instance,
sc config TCBuildAgent depend=EC2Config).
Alternatively, you can use the "Automatic (delayed start)" service starting mode.
Important note for images based on Windows Server 2016 image:
Due to the bug in the network settings, instance metadata is not available by default. It means the TeamCity agent service cannot retrieve its properties and cloud integration doesn't work (the agent does not connect to the server or is not automatically authorized). To fix this issue, do the following:
Install the latest EC2Config.
Set the dependency of the
TCBuildAgentservice on both
AmazonSSMAgentvia the command:
sc config TCBuildAgent depend=Ec2Config/AmazonSSMAgent.
Agent auto-upgrade Note
TeamCity agent auto-upgrades whenever distribution of agent plugins on the server changes (for example, after TeamCity upgrade). If you want to cut agent startup time, you might want to rebundle the agent AMI after agent plugins have been auto-updated.
Configuring an Amazon EC2 cloud profile
You can configure an Amazon EC2 agent cloud profile in the Cloud Profiles section of the Project Settings.
Custom Image Name
The value of the Custom Image Name parameter of the image serves as a unique identifier for all TeamCity agents using this image. For example, this value is added as a prefix to agents IDs in the cloud profiles log on the Agents | Cloud tab.
Each image in a cloud profile must have a unique custom name.
It is possible to use IAM (Identity and Access Management) profiles with build agents launched as Amazon EC2 instances, which requires the supplied AWS account to have the following permissions:
IAM profiles must be preconfigured in Amazon EC2. In the TeamCity web UI, the IAM profile drop-down menu enables you to select a role. Every new launched EC2 instance will assume the selected IAM role.
Amazon EC2 Spot Instances support
TeamCity supports Amazon EC2 spot instances which allows you to place your bid on unused EC2 capacity and use it, as long as your suggested price exceeds the current Spot price.
You can enable spot instances for an Amazon EC2 image in your cloud profile settings. Click Add image and select a Source, or edit an existing image. Select the Spot instances option, specify a Bid price, and save the image.
If the bid price is not specified, the default On-Demand price will be used.
TeamCity launches a spot instance as soon as the cloud profile is saved. If it is impossible to launch the instance (for example, if there is no available capacity or if your bid price is lower than the current minimum Spot Price in Amazon), TeamCity will be repeating the launch attempt once a minute, as long as there are queued builds which can run on this agent.
If a spot instance is terminated, TeamCity will fail the build with a corresponding build problem, and will re-add this build to the build queue.
Amazon EC2 Spot Fleet support
A spot fleet is a set of spot instances launched based on the predefined criteria. You can request a spot fleet instead of regular spot instances, and TeamCity will be able to select and launch spot instances with the lowest price in the availability zones you specify.
To use a spot fleet in your project:
In AWS Management Console, generate a spot fleet request:
Go to Instances | Spot Requests | Request Spot Instances.
Specify the required AMI, minimum compute unit, availability zones, and other request details.
Click JSON config to download a JSON file with the spot fleet configuration parameters. Note that only fields from the
SpotFleetRequestConfigDataclass are supported.
In TeamCity, add a spot fleet to a cloud profile:
On the Cloud Profile page click Add image.
In the Source drop-down menu, select Spot Instance Fleet. Enter the maximum number of required spot instances (Max instances) in a fleet and select an agent pool.
In the Spot Fleet Config field, insert the JSON configuration file generated in AWS Management Console.
Save the image.
To run the image, TeamCity will launch spot instances matching the allocation strategy specified in the spot fleet configuration.
Amazon EC2 Launch Templates support
TeamCity supports Amazon EC2 launch templates for cloud instances. Launch templates allow reusing a once defined launch specification for all new instances, which eliminates the need to describe the launch settings every time new instances are requested.
If your cloud profile is connected to the Amazon server, TeamCity will automatically detect launch templates available on this server. When adding an image, select a required template as the Source and specify its version, and TeamCity will request instances based on the template parameters. Optionally, you can also limit the number of launched instances and assign them to a certain agent pool.
When the default/latest version of the template is updated on the server, TeamCity will detect these changes and update the running instances.
Amazon EBS-Optimized Instances
The behavior of EBS optimization in TeamCity is similar to that offered by EC2 console. When configuring an image of the Amazon cloud profile, the optimization can be set using the corresponding box of the Instance Type. Note that
EBS optimization is turned on by default for
EBS optimization is turned off by default for any other instance types and can be turned on for instances that support it (such as
c3.xlarge, and so on)
Tagging for TeamCity-launched instances
The following requirements must be met for tagging instances launched by TeamCity:
you have the
the maximum number of tags (50) for your Amazon EC2 resource is not reached
In the absence of tagging permissions, TeamCity will still launch Amazon AMI and EBS images with no tags applied; Amazon EC2 spot instances will not be launched.
TeamCity enables users to get instance launch information by marking the created instances with the
teamcity:TeamcityData tag containing
<server UUID>:-<cloud profile ID>:-<image reference>. This tag is necessary for TeamCity integration with EC2 and must not be deleted.
Custom tags can be applied to EC2 cloud agent instances: when configuring Cloud profile settings, in the Add Image/Edit Image dialog use the Instance tags: field to specify tags in the format of
<key1>=<value1>,<key2>=<value2>. Amazon tag restrictions need to be considered.
When using the equal(=) sign in the tag value, no escaping is needed. For instance, the string
extraParam=name=John will be parsed into
<key=extraParam> and value
Tagging instance-dependent resources
When launching Amazon EC2 instances, TeamCity tags all the resources (for example, volumes and network adapters) associated with the created instances, which is important when evaluating the overall cost of an instance (taking into account the storage drive type and size, I/O operations (for standard drives), network (transfers out), and so on.
Sharing single EBS instance between several TeamCity servers
As mentioned above, TeamCity tags every instance it launches with the
teamcity:TeamcityData tag that represents a server, cloud profile, and source (AMI or EBS-instance). So, when several TeamCity servers try to use the same EBS instance, the second one will see the following message "Instance is used by another TeamCity server. Unable to start/stop it". If you are sure that no other TeamCity servers are working with this instance, you can delete the
teamcity:TeamcityData tag and the instance will become available for all TeamCity servers again.
New instance types
Since Amazon doesn't provide a robust API method to retrieve all instance types, Amazon integration relies on the periodical update of AWS SDK to make new instance types available.
However, there is a workaround if you are not willing to wait. To register new Instance Types, use the
teamcity.ec2.instance.types internal property with new instance types separated by ",".
If your TeamCity server needs to use a proxy to connect to AWS API endpoint, configure the following server internal properties to connect to Amazon AWS addresses.
teamcity.http.proxy.host.ec2— proxy server host name
teamcity.http.proxy.port.ec2— proxy server port
For proxy server authentication:
teamcity.http.proxy.user.ec2— proxy access username
teamcity.http.proxy.password.ec2— proxy access user password
For NTML authentication:
teamcity.http.proxy.domain.ec2— proxy user domain for NTLM authentication
teamcity.http.proxy.workstation.ec2— proxy access workstation for NTLM authentication
Estimating EC2 Costs
Usual Amazon EC2 pricing applies. Note that Amazon charges can depend on the specific configuration implemented to deploy TeamCity. We advise you to check your configuration and Amazon account data regularly in order to discover and prevent unexpected charges as early as possible.
Note that traffic volumes and necessary server and agent machines characteristics depend a big deal on the TeamCity setup and nature of the builds run. See also Estimate Hardware Requirements for TeamCity.
Here are some points to help you estimate TeamCity-related traffic:
If TeamCity server is not located within the same EC2 region or availability zone that is configured in TeamCity EC2 settings for agents, traffic between the server and agent is subject to usual Amazon EC2 external traffic charges.
When estimating traffic, bear in mind that there are lots types of traffic related to TeamCity (see a non-complete list below).
External connections originated by server:
Email and Jabber servers
Internal connections originated by server:
TeamCity agents (checking status, sending commands, retrieving information like thread dumps, and so on)
External connections originated by agent:
VCS servers (in case of agent-side checkout)
any connections performed from the build process itself
Internal connections originated by agent:
TeamCity server (retrieving build sources in case of server-side checkout or personal builds, downloading artifacts, and so on)
Usual connections served by the server:
As Amazon rounds machine uptime to the full hour for some configurations (more at How are Amazon EC2 instance hours billed?), adjust timeout setting on the EC2 image setting on TeamCity cloud integration settings according to your usual builds length.
It is also highly recommended to set execution timeout for all your builds so that a build hanging does not cause prolonged instance running with no payload.