AWS elasticbeanstalk documentation change
Summary
Updated role creation instructions to allow selecting existing roles (Service role and EC2 instance profile) instead of forcing new creation. Added conditional steps for role selection/creation and renumbered steps for clarity.
Security assessment
The changes improve documentation clarity about IAM role management but do not address a specific security vulnerability. While proper IAM role configuration is security-critical, the modifications focus on workflow improvements (allowing reuse of existing roles) rather than patching a security flaw or introducing new security controls. No evidence of a disclosed vulnerability or exploit mitigation is present.
Diff
diff --git a/elasticbeanstalk/latest/dg/GettingStarted.md b/elasticbeanstalk/latest/dg/GettingStarted.md index f7b449d84..707002f8b 100644 --- a//elasticbeanstalk/latest/dg/GettingStarted.md +++ b//elasticbeanstalk/latest/dg/GettingStarted.md @@ -82 +82 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y -###### To create the Service role +###### To create or select the Service role @@ -84 +84 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 1. For **Service role** , choose **Create role**. + 1. If you have previously created a **Service role** and would like to choose an existing one, select the value from the **Service role** drop-down and skip the remainder of these steps to create a Service role. @@ -86 +86 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 2. For **Trusted entity type** , choose **AWS service**. + 2. If you don't see any values listed for **Service role** , or you'd like to create a new one, continue with the next steps. @@ -88 +88 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 3. For **Use case** , choose **Elastic Beanstalk – Environment**. + 3. For **Service role** , choose **Create role**. @@ -90 +90 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 4. Choose **Next**. + 4. For **Trusted entity type** , choose **AWS service**. @@ -92 +92,5 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 5. Verify that **Permissions policies** include the following, then choose **Next** : + 5. For **Use case** , choose **Elastic Beanstalk – Environment**. + + 6. Choose **Next**. + + 7. Verify that **Permissions policies** include the following, then choose **Next** : @@ -98 +102,4 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 6. Choose **Create role**. + 8. Choose **Create role**. + + 9. Return to the **Configure service access** tab, refresh the list, then select the newly created service role. + @@ -100 +106,0 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 7. Return to the **Configure service access** tab, refresh the list, then select the newly created service role. @@ -102,0 +109 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y +###### To create or select an EC2 instance profile @@ -103,0 +111 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y + 1. If you have previously created an **EC2 instance profile** and would like to choose an existing one, select the value from the **EC2 instance profile** drop-down and skip the remainder of these steps to create an EC2 instance profile. @@ -105 +113 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y -###### To create the EC2 instance profile + 2. If you don't see any values listed for **EC2 instance profile** , or you'd like to create a new one, continue with the next steps. @@ -107 +115 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 1. Choose **Create role**. + 3. Choose **Create role**. @@ -109 +117 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 2. For **Trusted entity type** , choose **AWS service**. + 4. For **Trusted entity type** , choose **AWS service**. @@ -111 +119 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 3. For **Use case** , choose**Elastic Beanstalk – Compute**. + 5. For **Use case** , choose**Elastic Beanstalk – Compute**. @@ -113 +121 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 4. Choose **Next**. + 6. Choose **Next**. @@ -115 +123 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 5. Verify that **Permissions policies** include the following, then choose **Next** : + 7. Verify that **Permissions policies** include the following, then choose **Next** : @@ -123 +131 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 6. Choose **Create role**. + 8. Choose **Create role**. @@ -125 +133 @@ Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor y - 7. Return to the **Configure service access** tab, refresh the list, then select the newly created EC2 instance profile. + 9. Return to the **Configure service access** tab, refresh the list, then select the newly created EC2 instance profile.