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
Copy file name to clipboardExpand all lines: apigw-websocket-api-vpclink/README.md
+1-7Lines changed: 1 addition & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,8 @@ The SAM template deploys an Amazon API Gateway Websocket API endpoint with a VPC
4
4
5
5
Since Websocket APIs only support VPC Links associated with NLBs (Network Load Balancers), this pattern assumes that an internal NLB already exists in a VPC in the same Region.
6
6
7
-
<<<<<<< HEAD
8
-
Learn more about this pattern at Serverless Land Patterns: https://serverlessland.com/
9
7
=======
10
8
Learn more about this pattern at Serverless Land Patterns: https://serverlessland.com/patterns/apigw-rest-api-vpclink
11
-
>>>>>>> 79ec4deb37a6cd3b5e7b9877c6fa6e5175854d17
12
9
13
10
Important: this application uses various AWS services and there are costs associated with these services after the Free Tier usage - please see the AWS Pricing page for details. You are responsible for any AWS costs incurred. No warranty is implied in this example.
14
11
@@ -27,12 +24,9 @@ Important: this application uses various AWS services and there are costs associ
27
24
```
28
25
2. Change directory to the pattern directory:
29
26
```
30
-
<<<<<<< HEAD
31
27
cd apigw-websocket-api-vpclink
32
-
=======
33
-
cd apigw-rest-api-vpclink
34
-
>>>>>>> 79ec4deb37a6cd3b5e7b9877c6fa6e5175854d17
35
28
```
29
+
36
30
3. From the command line, use AWS SAM to deploy the AWS resources for the pattern as specified in the template.yml file:
0 commit comments