AWS elasticbeanstalk documentation change
Summary
Restructured environment creation steps with expanded IAM role configuration guidance, removed images, and updated terminology
Security assessment
Changes focus on improving IAM role creation procedures and environment configuration clarity rather than addressing specific vulnerabilities. While mentioning EC2 key pairs for secure access (existing security practice), this is not new security documentation but rather reorganization of existing content.
Diff
diff --git a/elasticbeanstalk/latest/dg/java-getstarted.md b/elasticbeanstalk/latest/dg/java-getstarted.md index f16ff338f..21442422e 100644 --- a//elasticbeanstalk/latest/dg/java-getstarted.md +++ b//elasticbeanstalk/latest/dg/java-getstarted.md @@ -29 +29 @@ Download any of the sample applications and deploy it to Elastic Beanstalk by fo -###### To launch an environment with a sample application (console) +###### To launch an environment with an application (console) @@ -35,5 +35 @@ Download any of the sample applications and deploy it to Elastic Beanstalk by fo - 3. On the application overview page, choose **Create new environment**. - -The following image displays the application overview page. - - + 3. On the application overview page, choose **Create environment**. @@ -59 +55 @@ Elastic Beanstalk supports multiple [versions](./concepts.platforms.html) for mo - 6. For **Application code** , you have some choices for launching a sample application. + 6. For **Application code** , you have several choices to proceed. @@ -63 +59 @@ Elastic Beanstalk supports multiple [versions](./concepts.platforms.html) for mo - * If you downloaded a sample application from this guide or another source, do the following steps. + * If you downloaded a sample application from this guide, or you have your own source code for an application, do the following steps. @@ -69 +65,3 @@ Elastic Beanstalk supports multiple [versions](./concepts.platforms.html) for mo - 3. Your computer's operating system will present you with an interface to select the local file that you downloaded. Select the source bundle file and continue. + 3. Your client machine's operating system will present you with an interface to select the local file that you downloaded. Select the source bundle file and continue. + + 7. Your choice for **Presets** depends on your purpose for the environment. @@ -71 +69,3 @@ Elastic Beanstalk supports multiple [versions](./concepts.platforms.html) for mo - 7. For **Presets** , choose **Single instance**. + * If you're creating a sample environment to learn about Elastic Beanstalk or a development environment, choose **Single instance (free tier eligible)**. + + * If you're creating a production environment or an environment to learn more about load balancing, choose one of the **High availability** options. @@ -75 +74,0 @@ Elastic Beanstalk supports multiple [versions](./concepts.platforms.html) for mo - 9. The **Configure service access** page displays. @@ -77 +75,0 @@ Elastic Beanstalk supports multiple [versions](./concepts.platforms.html) for mo -The following image illustrates the **Configure service access** page. @@ -79 +76,0 @@ The following image illustrates the **Configure service access** page. - @@ -81 +78 @@ The following image illustrates the **Configure service access** page. - 10. Choose a value from the **Existing Service Roles** dropdown. +###### To configure service access @@ -83 +80 @@ The following image illustrates the **Configure service access** page. - 11. (Optional) If you previously created an EC2 key pair, you can select it from the **EC2 key pair** field dropdown. You would use it to securely log in to the Amazon EC2 instance that Elastic Beanstalk provisions for your application. If you skip this step, you can always create and assign an EC2 key pair after the environment is created. For more information, see [EC2 key pair](./using-features.managing.security.html#using-features.managing.security.keypair). +Next, you need two roles. A _service role_ allows Elastic Beanstalk to monitor your EC2 instances and upgrade you environment’s platform. An _EC2 instance profile_ role permits tasks such as writing logs and interacting with other services. @@ -85 +82 @@ The following image illustrates the **Configure service access** page. - 12. Next, we'll focus on the **EC2 instance profile** dropdown list. The values displayed in this dropdown list may vary, depending on whether you account has previously created a new environment. +###### To create or select the Service role @@ -87 +84 @@ The following image illustrates the **Configure service access** page. -Choose one of the following items, based on the values displayed in your list. + 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. @@ -89 +86 @@ Choose one of the following items, based on the values displayed in your list. - * If `aws-elasticbeanstalk-ec2-role` displays in the dropdown list, select it from the dropdown list. + 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. @@ -91 +88 @@ Choose one of the following items, based on the values displayed in your list. - * If another value displays in the list, and it’s the default EC2 instance profile intended for your environments, select it from the dropdown list. + 3. For **Service role** , choose **Create role**. @@ -93 +90 @@ Choose one of the following items, based on the values displayed in your list. - * If the **EC2 instance profile** dropdown list doesn't list any values, you'll need to create an instance profile. + 4. For **Trusted entity type** , choose **AWS service**. @@ -95 +92 @@ Choose one of the following items, based on the values displayed in your list. -###### Create an instance profile + 5. For **Use case** , choose **Elastic Beanstalk – Environment**. @@ -97 +94 @@ Choose one of the following items, based on the values displayed in your list. -To create an instance profile, we'll take a detour to another procedure on this same page. Go to the end of this procedure and expand the procedure that follows, _Create IAM Role for EC2 instance profile_. + 6. Choose **Next**. @@ -99 +96 @@ To create an instance profile, we'll take a detour to another procedure on this -Complete the steps in _Create IAM Role for EC2 instance profile_ to create an IAM Role that you can subsequently select for the EC2 instance profile. Then return back to this step. + 7. Verify that **Permissions policies** include the following, then choose **Next** : @@ -101 +98 @@ Complete the steps in _Create IAM Role for EC2 instance profile_ to create an IA -Now that you've created an IAM Role, and refreshed the list, it displays as a choice in the dropdown list. Select the IAM Role you just created from the **EC2 instance profile** dropdown list. + * `AWSElasticBeanstalkEnhancedHealth` @@ -103 +100 @@ Now that you've created an IAM Role, and refreshed the list, it displays as a ch - 13. Choose **Skip to Review** on the **Configure service access** page. + * `AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy` @@ -105 +102 @@ Now that you've created an IAM Role, and refreshed the list, it displays as a ch -This will select the default values for this step and skip the optional steps. + 8. Choose **Create role**. @@ -107 +104 @@ This will select the default values for this step and skip the optional steps. - 14. The **Review** page displays a summary of all your choices. + 9. Return to the **Configure service access** tab, refresh the list, then select the newly created service role. @@ -109 +105,0 @@ This will select the default values for this step and skip the optional steps. -To further customize your environment, choose **Edit** next to the step that includes any items you want to configure. You can set the following options only during environment creation: @@ -111 +106,0 @@ To further customize your environment, choose **Edit** next to the step that inc - * Environment name @@ -113 +107,0 @@ To further customize your environment, choose **Edit** next to the step that inc - * Domain name @@ -115 +109 @@ To further customize your environment, choose **Edit** next to the step that inc - * Platform version +###### To create or select an EC2 instance profile @@ -117 +111 @@ To further customize your environment, choose **Edit** next to the step that inc - * Processor + 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. @@ -119 +113 @@ To further customize your environment, choose **Edit** next to the step that inc - * VPC + 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. @@ -121 +115 @@ To further customize your environment, choose **Edit** next to the step that inc - * Tier + 3. Choose **Create role**. @@ -123 +117 @@ To further customize your environment, choose **Edit** next to the step that inc -You can change the following settings after environment creation, but they require new instances or other resources to be provisioned and can take a long time to apply: + 4. For **Trusted entity type** , choose **AWS service**. @@ -125 +119 @@ You can change the following settings after environment creation, but they requi - * Instance type, root volume, key pair, and AWS Identity and Access Management (IAM) role + 5. For **Use case** , choose**Elastic Beanstalk – Compute**. @@ -127 +121 @@ You can change the following settings after environment creation, but they requi - * Internal Amazon RDS database + 6. Choose **Next**. @@ -129 +123 @@ You can change the following settings after environment creation, but they requi - * Load balancer + 7. Verify that **Permissions policies** include the following, then choose **Next** : @@ -131 +125 @@ You can change the following settings after environment creation, but they requi -For details on all available settings, see [The create new environment wizard](./environments-create-wizard.html). + * `AWSElasticBeanstalkWebTier` @@ -133 +127 @@ For details on all available settings, see [The create new environment wizard](. - 15. Choose **Submit** at the bottom of the page to initialize the creation of your new environment. + * `AWSElasticBeanstalkWorkerTier` @@ -134,0 +129 @@ For details on all available settings, see [The create new environment wizard](. + * `AWSElasticBeanstalkMulticontainerDocker` @@ -135,0 +131 @@ For details on all available settings, see [The create new environment wizard](. + 8. Choose **Create role**. @@ -136,0 +133 @@ For details on all available settings, see [The create new environment wizard](. + 9. Return to the **Configure service access** tab, refresh the list, then select the newly created EC2 instance profile. @@ -138 +134,0 @@ For details on all available settings, see [The create new environment wizard](. - @@ -140 +135,0 @@ For details on all available settings, see [The create new environment wizard](. -###### To create the EC2 instance profile @@ -142 +136,0 @@ For details on all available settings, see [The create new environment wizard](. - 1. Choose **Create role**. @@ -144 +138 @@ For details on all available settings, see [The create new environment wizard](. - 2. For **Trusted entity type** , choose **AWS service**. +###### To finish configuring and creating your application @@ -146 +140 @@ For details on all available settings, see [The create new environment wizard](. - 3. For **Use case** , choose**Elastic Beanstalk – Compute**. + 1. (Optional) If you previously created an EC2 key pair, you can select it from the **EC2 key pair** field dropdown. You would use it to securely log in to the Amazon EC2 instance that Elastic Beanstalk provisions for your application. If you skip this step, you can always create and assign an EC2 key pair after the environment is created. For more information, see [EC2 key pair](./using-features.managing.security.html#using-features.managing.security.keypair). @@ -148 +142 @@ For details on all available settings, see [The create new environment wizard](. - 4. Choose **Next**. + 2. Choose **Skip to Review** on the **Configure service access** page. @@ -150 +144 @@ For details on all available settings, see [The create new environment wizard](. - 5. Verify that **Permissions policies** include the following, then choose **Next** : + 3. The **Review** page displays a summary of all your choices. @@ -152 +146 @@ For details on all available settings, see [The create new environment wizard](. - * `AWSElasticBeanstalkWebTier` +To further customize your environment, choose **Edit** next to the step that includes any items you want to configure. You can set the following options only during environment creation: @@ -154 +148 @@ For details on all available settings, see [The create new environment wizard](. - * `AWSElasticBeanstalkWorkerTier` + * Environment name @@ -156 +150,13 @@ For details on all available settings, see [The create new environment wizard](. - * `AWSElasticBeanstalkMulticontainerDocker` + * Domain name + + * Platform version + + * Processor + + * Load balancer type + + * Tier + +You can change the following settings after environment creation, but they require new instances or other resources to be provisioned and can take a long time to apply: + + * Instance type, root volume, key pair, and AWS Identity and Access Management (IAM) role @@ -158 +164,5 @@ For details on all available settings, see [The create new environment wizard](. - 6. Choose **Create role**. + * Internal Amazon RDS database + + * VPC + +For details on all available settings, see [The create new environment wizard](./environments-create-wizard.html). @@ -160 +170 @@ For details on all available settings, see [The create new environment wizard](. - 7. Return to the **Configure service access** tab, refresh the list, then select the newly created EC2 instance profile. + 4. Choose **Submit** at the bottom of the page to initialize the creation of your new environment.