You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add `%USERPROFILE%\AppData\Roaming\Python\Scripts` to your PATH variable. Search for **Edit environment variables for your account.** in the Start menu.
25
+
Add `%USERPROFILE%\AppData\Roaming\Python\Scripts` to your PATH variable. Search for **Edit environment variables for your account** in the Start menu.
26
26
27
27
If you don't have pip, follow the instructions [here](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-install.html).
28
28
29
-
## Download and extract WordPress and the configuration files
1. Configure a local EB CLI repository with the PHP platform. Choose a [supported region](http://docs.aws.amazon.com/general/latest/gr/rande.html#elasticbeanstalk_region) that is close to you.
2. Configure SSH. Create a key that Elastic Beanstalk will assign to the EC2 instances in your environment to allow you to connect to them later. You can also choose an existing key pair if you have the private key locally.
56
+
57
+
~/wordpress-beanstalk$ eb ssh --setup
58
+
59
+
3. Create an Elastic Beanstalk environment with a MySQL database.
Modify the configuration files in the .ebextensions folder with the IDs of your [default VPC and subnets](https://console.aws.amazon.com/vpc/home#subnets:filter=default), and [your public IP address](https://www.google.com/search?q=what+is+my+ip).
@@ -50,7 +71,7 @@ Deploy the project code to your Elastic Beanstalk environment.
50
71
51
72
First, confirm that your environment is `Ready` with `eb status`. Environment creation takes about 15 minutes due to the RDS DB instance provisioning time.
52
73
53
-
```
74
+
```Shell
54
75
~/wordpress-beanstalk$ eb status
55
76
~/wordpress-beanstalk$ eb deploy
56
77
```
@@ -59,13 +80,13 @@ First, confirm that your environment is `Ready` with `eb status`. Environment cr
59
80
60
81
This project includes a configuration file (`loadbalancer-sg.config`) that creates a security group and assigns it to the environment's load balancer, using the IP address that you configured in `ssh.config` to restrict HTTP access on port 80 to connections from your network. Otherwise, an outside party could potentially connect to your site before you have installed WordPress and configured your admin account.
61
82
62
-
You can [view the related SGs in the EC2 console](https://console.aws.amazon.com/ec2/v2/home#SecurityGroups:search=wordpress-beanstalk)
83
+
You can [view the related SGs in the EC2 console](https://console.aws.amazon.com/ec2/v2/home#SecurityGroups:search=wordpress-beanstalk). In the top right corner, choose the region in which you created your environment.
63
84
64
85
## Install WordPress
65
86
66
87
Open your site in a browser.
67
88
68
-
```
89
+
```Shell
69
90
~/wordpress-beanstalk$ eb open
70
91
```
71
92
@@ -83,7 +104,7 @@ The hash salt can be any value but shouldn't be stored in source control. Use `e
Scale up to run the site on multiple instances for high availability.
123
+
```Shell
124
+
~/wordpress-beanstalk$ eb scale 3
101
125
```
126
+
127
+
When the update completes, open the site.
128
+
129
+
```Shell
102
130
~/wordpress-beanstalk$ eb open
103
131
```
104
132
105
-
Finally, scale up to run the site on multiple instances for high availability.
106
-
```
107
-
~/wordpress-beanstalk$ eb scale 3
108
-
```
133
+
Refresh the site several times to verify that all instances are reading from the EFS file system. Create posts and upload files to confirm functionality.
0 commit comments