docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update aws.md (#2593)

This commit is contained in:
Wang Jie 2017-04-04 06:22:11 +08:00 committed by John Mulhausen
parent ccfb68a8fa
commit a40e346431
1 changed files with 14 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
datacenter/install/aws.md
View File

@ -37,7 +37,7 @@ in your worker Auto Scaling group (via the AWS console, or updating the
automatically join the swarm. This architecture ensures that both manager
and worker nodes are spread across multiple AZs for resiliency and
high-availability. The template is adjustable and upgradeable meaning you can
adjust your configuration (e.g instance types or Docker engine version)
adjust your configuration (e.g instance types or Docker engine version).
## Prerequisites
@ -52,9 +52,9 @@ in your worker Auto Scaling group (via the AWS console, or updating the
- S3 Bucket
- SSH key in AWS in the region where you want to deploy (required to access the completed Docker install)
- AWS account that support EC2-VPC
- AWS account that supports EC2-VPC
For more information about adding an SSH key pair to your account, please refer to the [Amazon EC2 Key Pairs docs](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html)
For more information about adding an SSH key pair to your account, please refer to the [Amazon EC2 Key Pairs docs](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html).
## Cloudformation Parameters
@ -95,6 +95,7 @@ Enable if you want Docker for AWS to automatically cleanup unused space on your
When enabled, `docker system prune` will run staggered every day, starting at 1:42AM UTC on both workers and managers. The prune times are staggered slightly so that not all nodes will be pruned at the same time. This limits resource spikes on the swarm.
Pruning removes the following:
- All stopped containers
- All volumes not used by at least one container
- All dangling images
@ -156,7 +157,7 @@ landing pages:
![dtr.png](../images/dtr.png){: .with-border}
> Note: During the installation process, a self-signed certificate is generated
> **Note**: During the installation process, a self-signed certificate is generated
for both UCP and DTR. You can replace these certificates with your own
CA-signed certificate after the installation is complete. When you access UCP
and DTR URLs for the first time, you need to proceed insecurely (multiple times)
@ -170,10 +171,10 @@ names. To do that, please follow the instructions below:
1. Create an A or CNAME DNS record for UCP and DTR pointing to the UCP and DTR
ELB DNS/IP. You can find the ELB names in the **Output** tab.
2. Login to DTR using the DTR ELB URL and go to **Settings** page.
2. Log in to DTR using the DTR ELB URL and go to **Settings** page.
3. Update the **Domain** section with the your DNS and their respective
certificate. Make sure you click **Save** at the end.
4. Login to UCP using the UCP ELB URL and go to **Admin Settings** tab.
4. Log in to UCP using the UCP ELB URL and go to **Admin Settings** tab.
5. Under the **Cluster Configuration** update **EXTERNAL SERVICE LOAD BALANCER**
with your custom UCP DNS name. Then click on **Update Settings**.
6. Under the **Certificates** section, upload or paste your own certificates for
@ -204,7 +205,7 @@ Once you download the bundle and load it, run the following command:
Once you run this Docker container, you'll be requested to choose a replica
to reconfigure. Press **Enter** to proceed with the chosen one.
8. Now you may access UCP and DTR with your own custom DNS names
8. Now you may access UCP and DTR with your own custom DNS names.
## Deploy and Access Your Applications on Docker Enterprise Edition
@ -305,7 +306,7 @@ Changing manager count live is **_not_** currently supported.
### AWS Console
Login to the AWS console, and go to the EC2 dashboard. On the lower left hand
Log in to the AWS console, and go to the EC2 dashboard. On the lower left hand
side select the "Auto Scaling Groups" link.
Look for the Auto Scaling group with the name that looks like
@ -328,7 +329,7 @@ pool until it reaches the new size.
### CloudFormation Update
Go to the CloudFormation management page, and click the checkbox next to the
stack you want to update. Then Click on the action button at the top, and
stack you want to update. Then click on the action button at the top, and
select "Update Stack".
![console_installation.png](../images/cloudformation_update.png){: .with-border}