Skip to content

Commit 09f4693

Browse files
committed
update readme links
1 parent 1a1448c commit 09f4693

File tree

1 file changed

+23
-23
lines changed

1 file changed

+23
-23
lines changed

README.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Learn Aws Lambda
22

3-
![aws lambda intro image](http://i.imgur.com/9ImDKrv.jpg)
3+
![aws lambda intro image](https://i.imgur.com/9ImDKrv.jpg)
44

55
Learn to use AWS Lambda to create scalable micro-services in less time
66
and cost *far* less to run than "*traditional*" server-based apps.
@@ -56,7 +56,7 @@ so you cannot store data or the `result` of an operation *locally*.
5656
The lack of *local* persistence on Lambda is resolved by having
5757
low-latency access to AWS S3 and *other* AWS Datastores e.g:
5858
[ElastiCache](https://aws.amazon.com/elasticache/) (in-memory cache),
59-
[DynamoDB](http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Introduction.html) (NoSQL ssd-based database),
59+
[DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Introduction.html) (NoSQL ssd-based database),
6060
[RDS](https://aws.amazon.com/rds/) (*relational database*),
6161
however there's an
6262
important (and potentially *expensive*) catch: PUT/POST/GET requests to all
@@ -65,9 +65,9 @@ something to S3 on each execution cycle you could rack up the bill!
6565

6666
## *How*?
6767

68-
+ General Intro (*if you're completely new, watch the video!*): http://aws.amazon.com/lambda/
69-
+ How it Works: http://docs.aws.amazon.com/lambda/latest/dg/lambda-introduction.html
70-
+ Getting Started Guide (Overview): http://docs.aws.amazon.com/lambda/latest/dg/welcome.html
68+
+ General Intro (*if you're completely new, watch the video!*): https://aws.amazon.com/lambda/
69+
+ How it Works: https://docs.aws.amazon.com/lambda/latest/dg/lambda-introduction.html
70+
+ Getting Started Guide (Overview): https://docs.aws.amazon.com/lambda/latest/dg/welcome.html
7171

7272
## Create and Test Your Own AWS Lambda Function
7373

@@ -89,7 +89,7 @@ something to S3 on each execution cycle you could rack up the bill!
8989

9090
Here's a super simple walkthrough of a 'HELLO WORLD!' example to help get you started with AWS Lambda:
9191

92-
1. If you haven't already done so, create a free AWS account **[here](http://aws.amazon.com/)**.
92+
1. If you haven't already done so, create a free AWS account **[here](https://aws.amazon.com/)**.
9393

9494
2. Sign in to the AWS management console, select your region in the top right hand corner and then open the AWS Lambda console.
9595

@@ -100,7 +100,7 @@ Here's a super simple walkthrough of a 'HELLO WORLD!' example to help get you st
100100
5. Once you have found this follow the instructions given to set up your function.
101101
This will include setting a role (a role is an AWS identity with permission
102102
policies that determine what the identity can or cannot do in AWS. For more
103-
information on roles click **[here](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**).
103+
information on roles click **[here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)**).
104104
Like the tutorial suggests we chose the 'lambda_basic_execution' role because our function is extremely simple.
105105

106106
6. AWS Lambda expects us to export an object which has a property called handler.
@@ -286,7 +286,7 @@ exports.handler = function(event, context) {
286286
```
287287

288288
For *even* more steps on enabling API Keys on AWS API Gateway,
289-
see: http://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-api-keys.html
289+
see: https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-api-keys.html
290290

291291

292292
<br />
@@ -642,7 +642,7 @@ Give your message a subject and add some text to the message body. Leave the 'Ti
642642
643643
![Publish message](https://cloud.githubusercontent.com/assets/5912647/12579968/c3410dec-c423-11e5-9189-3dd68fe7060c.png)
644644
645-
NB: Using the JSON Messsage Generator option it is possible to format messages differently for different viewing platforms. Find out more on the [AWS SNS docs](http://docs.aws.amazon.com/sns/latest/dg/PublishTopic.html).
645+
NB: Using the JSON Messsage Generator option it is possible to format messages differently for different viewing platforms. Find out more on the [AWS SNS docs](https://docs.aws.amazon.com/sns/latest/dg/PublishTopic.html).
646646
647647
#### Viewing the output of the lambda Function
648648
@@ -768,7 +768,7 @@ NB: Using the JSON Messsage Generator option it is possible to format messages d
768768
})
769769
```
770770
771-
More info on testing lambda functions locally can be found [here](https://medium.com/@AdamRNeary/developing-and-testing-amazon-lambda-functions-e590fac85df4#.romz6yjwv) and an example of testing by mocking the context object can be found [here](http://codedad.net/2016/01/03/test-aws-lambda-function-without-aws/).
771+
More info on testing lambda functions locally can be found [here](https://medium.com/@AdamRNeary/developing-and-testing-amazon-lambda-functions-e590fac85df4#.romz6yjwv) and an example of testing by mocking the context object can be found [here](https://codedad.net/2016/01/03/test-aws-lambda-function-without-aws/).
772772
773773
3. **Using grunt-aws-lambda plugin**
774774
@@ -783,7 +783,7 @@ Start by creating a blank AWS Lambda function that will be called whenever a new
783783
#### Set up SES
784784
For this you need your own domain, and you need to verify the domain with AWS, this can take up to 72hrs, so have a nice drink and chill out while you wait :sunglasses: :coffee:
785785
786-
See here for how: http://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-domain-procedure.html
786+
See here for how: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-domain-procedure.html
787787
788788
#### Add a rule set
789789
Click `rule sets` on the bottom left and create a new rule set with whatever name you like. If you want to have your function triggered by emails sent to any address in your domain you can leave recipient blank, else you can add the recipient you want to trigger the function.
@@ -1050,7 +1050,7 @@ In this example will build a script that will execute the neccessary steps to up
10501050

10511051
We will be writing our own bash script that will involve the use of some of the AWS CLI commands. Follow these instructions on how to get set up with the AWS CLI on your local machine:
10521052

1053-
1. If you haven't already done so, set up an account with AWS **[here](http://aws.amazon.com/)**.
1053+
1. If you haven't already done so, set up an account with AWS **[here](https://aws.amazon.com/)**.
10541054

10551055
2. You'll then need to get your 'access key ID' and 'secret access key' by doing the following:
10561056
* Open the IAM console
@@ -1062,7 +1062,7 @@ We will be writing our own bash script that will involve the use of some of the
10621062
* Secret Access Key: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
10631063
* Click 'Download Credentials' and store them in a secure location
10641064
1065-
3. Install the AWS CLI via a method of your choice **[here](http://docs.aws.amazon.com/cli/latest/userguide/installing.html)**.
1065+
3. Install the AWS CLI via a method of your choice **[here](https://docs.aws.amazon.com/cli/latest/userguide/installing.html)**.
10661066
10671067
4. Once it's installed you have to configure it. Type ```aws configure``` in the command line. You should see something like this:
10681068
```bash
@@ -1567,7 +1567,7 @@ Using aliases means that calling event source doesn't have to know the specific
15671567
* new versions to easily be promoted or rolled back (aliases can easily be mapped to different function versions)
15681568
* easier event source mappings - more control over which versions of your function are used with specific event sources in your development environment
15691569
1570-
Walkthrough of implementing [versioning](http://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases-walkthrough1.html) and [aliasing](http://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases-walkthrough1.html) using the AWS CLI on the AWS Lambda docs.
1570+
Walkthrough of implementing [versioning](https://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases-walkthrough1.html) and [aliasing](https://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases-walkthrough1.html) using the AWS CLI on the AWS Lambda docs.
15711571
15721572
### Create an API with GET/POST Methods that uses Lambda functions to retrieve/update records from a DynamoDB table
15731573
@@ -1829,7 +1829,7 @@ Here are the steps to set up the Serverless example project 'serverless-starter'
18291829
18301830
![user summary](https://cloud.githubusercontent.com/assets/12450298/12822489/39388622-cb60-11e5-900d-bda80d95cd5f.png)
18311831
1832-
3. Next you're going to have to install the AWS CLI if you haven't already done so. You can do so via any of the methods **[here](http://docs.aws.amazon.com/cli/latest/userguide/installing.html)**. Once you've done that, type the ```aws configure``` command into the command line. Use the Access ID and Secret Access ID from the user you just set up, select your region and then press enter for the last option:
1832+
3. Next you're going to have to install the AWS CLI if you haven't already done so. You can do so via any of the methods **[here](https://docs.aws.amazon.com/cli/latest/userguide/installing.html)**. Once you've done that, type the ```aws configure``` command into the command line. Use the Access ID and Secret Access ID from the user you just set up, select your region and then press enter for the last option:
18331833
18341834
```bash
18351835
$ aws configure
@@ -1945,14 +1945,14 @@ _(The Serverless framework automates a lot of the processes that we have covered
19451945
## Further Reading
19461946
19471947
+ Walkthrough Custom Events:
1948-
http://docs.aws.amazon.com/lambda/latest/dg/walkthrough-custom-events.html
1948+
https://docs.aws.amazon.com/lambda/latest/dg/walkthrough-custom-events.html
19491949
+ Admin Events:
1950-
http://docs.aws.amazon.com/lambda/latest/dg/walkthrough-s3-events-adminuser.html
1951-
+ lambdash: AWS Lambda Shell Hack http://alestic.com/2014/11/aws-lambda-shell
1952-
+ Lambda Persistence: http://alestic.com/2014/12/aws-lambda-persistence
1953-
+ Lambda Speed (faster execution): http://alestic.com/2014/11/aws-lambda-speed
1950+
https://docs.aws.amazon.com/lambda/latest/dg/walkthrough-s3-events-adminuser.html
1951+
+ lambdash: AWS Lambda Shell Hack https://alestic.com/2014/11/aws-lambda-shell
1952+
+ Lambda Persistence: https://alestic.com/2014/12/aws-lambda-persistence
1953+
+ Lambda Speed (faster execution): https://alestic.com/2014/11/aws-lambda-speed
19541954
+ Lambda Execution Environment and Available Libraries:
1955-
http://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html
1955+
https://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html
19561956
+ Intro to Lambda by [Jeff Douglas](https://github.com/jeffdonthemic) (*Cloud Legend*)
19571957
https://www.topcoder.com/blog/amazon-lambda-demo-tutorial/ + https://youtu.be/m7egclrPzSg
19581958
+ Alternatives to Lambda:
@@ -1974,7 +1974,7 @@ As exciting as this *incredible* service is, it's only natural to have few conce
19741974
19751975
AWS Lambda has a default safety throttle limit of **100 concurrent Lambda
19761976
function executions** per account.
1977-
see: http://docs.aws.amazon.com/lambda/latest/dg/limits.html
1977+
see: https://docs.aws.amazon.com/lambda/latest/dg/limits.html
19781978
19791979
***Q***: Does this mean we can "*only*" process 100 requests at any given time?
19801980
***A***: No, *it depends* on how long the Lambda function takes to *complete*.
@@ -2044,7 +2044,7 @@ event notification or invoke call, including test invokes from the console.
20442044
+ Execution time is rounded up to the nearest 100ms
20452045
+ You are charged $0.00001667 for every GB-second used
20462046
2047-
See: http://aws.amazon.com/lambda/pricing/ for more ***pricing examples***.
2047+
See: https://aws.amazon.com/lambda/pricing/ for more ***pricing examples***.
20482048
20492049
## FAQ
20502050

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy