AWS codebuild documentation change
Summary
Added documentation for manually specifying EC2 instances, restructured fleet creation steps, added VPC configuration options, and clarified custom AMI usage.
Security assessment
The changes primarily focus on feature enhancements (custom instance selection, VPC connectivity, and AMI configuration) without addressing specific security vulnerabilities. While VPC and custom AMI configurations can improve security posture, the documentation updates are operational rather than security advisories. No evidence of patching vulnerabilities or addressing security incidents.
Diff
diff --git a/codebuild/latest/userguide/fleets.md b/codebuild/latest/userguide/fleets.md index c28d8ecf0..9b311264b 100644 --- a//codebuild/latest/userguide/fleets.md +++ b//codebuild/latest/userguide/fleets.md @@ -5 +5 @@ -Create a reserved capacity fleetBest practicesCan I share a reserved capacity fleet across multiple CodeBuild projects?How does attribute-based compute work?Which regions support reserved capacity fleets?How do I configure a reserved capacity macOS fleet?How do I configure a custom Amazon Machine Image (AMI) for a reserved capacity fleet?Limitations of reserved capacity fleets +Create a reserved capacity fleetBest practicesCan I share a reserved capacity fleet across multiple CodeBuild projects?How does attribute-based compute work?Can I manually specify an Amazon EC2 instance for my fleet?Which regions support reserved capacity fleets?How do I configure a reserved capacity macOS fleet?How do I configure a custom Amazon Machine Image (AMI) for a reserved capacity fleet?Limitations of reserved capacity fleets @@ -39,0 +40,2 @@ Regardless of how long you run an instance for, reserved capacity fleets incur a + * Can I manually specify an Amazon EC2 instance for my fleet? + @@ -71,7 +73 @@ Use the following instructions to create a reserved capacity fleet. - 6. From the **Environment type** drop-down menu, choose the environment type. - - 7. For **vCPUs** , choose the number of vCPUs to include in your fleet. - - 8. For **Memory** , choose the amount of memory to include in your fleet. - - 9. For **Disk** , choose the amount of disk space to include in your fleet. + 6. (Optional) Select **Use instance running mode - optional** to run on an Amazon EC2 instance directly instead of a Docker container. Then choose a **Major version** and **Minor version**. @@ -79 +75 @@ Use the following instructions to create a reserved capacity fleet. - 10. To provide lower latency I/O performance, select **Use NVMe SSD instance store**. + 7. (Optional) In **Additional configuration** do the following: @@ -81 +77 @@ Use the following instructions to create a reserved capacity fleet. - 11. In the **Capacity** text field, enter the minimum number of instances in the fleet. + * Select **Configure VPC - optional** to connect your fleet to a VPC to access private resources during usage. @@ -83,5 +79 @@ Use the following instructions to create a reserved capacity fleet. - 12. In the **Overflow behavior** field, choose the behavior when demand exceeds the fleet capacity. For more information about these options, see [Reserved capacity fleet properties](./fleets.reserved-capacity-fleets.html). - - 13. (Optional) In **Additional configuration** do the following: - - * From the **VPC - optional** drop-down menu, select a VPC that your CodeBuild fleet will access. + * From the **VPC** drop-down menu, select a VPC that your CodeBuild fleet will access. @@ -105 +97,11 @@ Make sure that your fleet role has the necessary permissions. For more informati - 14. Choose **Create compute fleet**. + * Select **Configure custom AMI - optional** to use a custom Amazon Machine Image (AMI). + + * From the **AMI** drop-down menu, select a an Amazon Machine Image (AMI) for your fleet. + + * In the **Fleet Service Role** field, choose an existing service role. + +###### Note + +Make sure that your fleet role has the necessary permissions. For more information, see [Allow a user to add a permission policy for a fleet service role](./auth-and-access-control-iam-identity-based-access-control.html#customer-managed-policies-example-permission-policy-fleet-service-role). + + 8. In **Capacity configuration** , from **Compute selection mode** , choose one of the following: @@ -107 +109,25 @@ Make sure that your fleet role has the necessary permissions. For more informati - 15. After the compute fleet is created, create a new CodeBuild project or edit an existing one. From **Environment** , choose **Reserved capacity** under **Provisioning model** , and then choose the specified fleet under **Fleet name**. + * If you choose **Guided selection** , do the following: + + * For **Compute** , choose the type of instances included in this fleet. + + * In the **Capacity** text field, enter the minimum number of instances in the fleet. + + * (Optional) In **Additional configuration** do the following: + + * Select **Configure scaling - optional** to automatically scale your fleet based on this configuration. From the **Scaling mode - optional** drop-down menu, choose the behavior when demand exceeds the fleet capacity. + + * If you choose **Custom instance** , do the following: + + * From the **Compute instance type** drop-down menu, select the type of instances included in this fleet. + + * In the **Additional EBS volume size - optional** text field, enter the volume additional to the 64GB of disk space provided. + + * In the **Capacity** text field, enter the minimum number of instances in the fleet. + + * (Optional) In **Additional configuration** do the following: + + * Select **Configure scaling - optional** to automatically scale your fleet based on this configuration. From the **Scaling mode - optional** drop-down menu, choose the behavior when demand exceeds the fleet capacity. + + 9. Choose **Create compute fleet**. + + 10. After the compute fleet is created, create a new CodeBuild project or edit an existing one. From **Environment** , choose **Reserved capacity** under **Provisioning model** , and then choose the specified fleet under **Fleet name**. @@ -140,0 +167,4 @@ If you input a `computeConfiguration` that is not possible to satisfy in CodeBui +## Can I manually specify an Amazon EC2 instance for my fleet? + +Yes, you can directly input your desired Amazon EC2 instance in the console by selecting **Custom instance** or by configuring the API parameter, `InstanceType`. This field is used in the following APIs: CreateFleet, UpdateFleet, CreateProject, UpdateProject and StartBuild. For more information, see [Compute instance type](./fleets.reserved-capacity-fleets.html#compute). +