Skip to content

Commit 18112fd

Browse files
Update README.md
1 parent 94b1aa9 commit 18112fd

File tree

1 file changed

+4
-13
lines changed

1 file changed

+4
-13
lines changed

README.md

Lines changed: 4 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -188,7 +188,7 @@ git clone https://github.com/aws-solutions-library-samples/guidance-for-using-fl
188188
```bash
189189
cd guidance-for-using-floating-virtual-fixed-ip-address-with-load-balancing-on-aws
190190
```
191-
6. Download the node dependencies using command:
191+
6. Download the node.js dependencies using command:
192192
```bash
193193
npm install
194194
```
@@ -207,13 +207,13 @@ cdk deploy VpcStack --require-approval never --method=direct
207207
```bash
208208
sh prepare-cdk-json.sh default
209209
```
210-
to automatically prepare for `cdk.json` based on the instracture deployed in previous step.
210+
to automatically prepare contents of `cdk.json` configuration file for AWS CDK deployment based on the instracture deployed in previous step.
211211
The contents of `cdk.json` can be prepared manually: Look for the Output from previous step, and replace placeholders `ENTER-VALUE` in the file with appropriate values from that ouput.
212212

213213
### (Part 2) Deploy the guidance:
214214

215-
10. Configure `cdk.json`. Replace `ENTER-VALUE` placeholders with real values. Those values come from preexisting infrastructure. If the part one(basic infrastructure) of this deployment was executed, the file is already prepared and ready to be used.
216-
11. Deploy this guidance using command:
215+
10. Configure `cdk.json`. Replace `ENTER-VALUE` placeholders with actual values - those values come from preexisting infrastructure. If the part one(basic infrastructure) of this deployment was executed, this file is already configured with proper parameter values and ready to be used.
216+
11. Deploy the guidance using command:
217217
```bash
218218
cdk deploy ApplicationStack --require-approval never --method=direct
219219
```
@@ -232,15 +232,6 @@ If the Part one (see above) was deployed, there should be route for `IP = 20.0.0
232232

233233
## Running the Guidance
234234

235-
<!--
236-
<Provide instructions to run the Guidance with the sample data or input provided, and interpret the output received.>
237-
This section should include:
238-
239-
* Guidance inputs
240-
* Commands to run
241-
* Expected output (provide screenshot if possible)
242-
* Output description
243-
-->
244235
Since the guidance is satisfying a specific technical requirement for a static, single IP address to access an IT system from within the private network, it can be used by a client application that needs to access a AWS resource(s) using such floating virtual IP address in that network as an endpoint.
245236

246237
## Cleanup

0 commit comments

Comments
 (0)