- AWS CLI - Zainstaluj AWS CLI
- SAM CLI - Zainstaluj SAM CLI
- Java8 - Zainstaluj Java SE Development Kit 8
- Docker - Zainstaluj Docker community edition
- Gradle - Zainstaluj Gradle
Uwaga nie biorę odpowiedzialności jeżeli jakiekolwiek inne narzędzie przestanie działać to jest mój prod setup na WIN
Instalujemy chocolatey
Następnie instalujemy JDK8, gradle i maven'a jak kto chce
choco install jdk8
choco install gradle
choco install maven
To zainstaluje nam wszystkie rzeczy od strony Javy potrzebnych do zbudowania aplikacji i ustawi odpowiednio $PATH
Szybki tutor
- Zaloguj się na https://aws.amazon.com/education/awseducate/ za pomocą konta studenckiego
- Wybierz
My Classroms
- Przejdź do klasy
Cloud Computing systems
- Wybierz
Account Details
i rozwiń opcjęAWS CLI
- Skopiuj wyświetloną zawartość do pliku
~/.aws/credentials
Przykład:
[default]
aws_access_key_id=KeysEveryWhere
aws_secret_access_key=WhyYouWantToKnowThat
aws_session_token=SomethingVeryLong
- Pod poleceniem
aws configure
powinny się wyświetlić prawidłowo dane
Pamiętaj że musi być uruchomiony docker aby uruchomić aplikację
sam build
sam local start-api
Za pomocą sam local invoke
sam local invoke HelloFunction --event events/event.json
Jezeli wszystko zrobione poprawnie powinno zwrócić taki json
{"body":"{ \"message\": \"hello world\", \"location\": \"ip-number\" }","headers":{"X-Custom-Header":"application/json","Content-Type":"application/json"},"statusCode":200}
Do bazy mozemy korzystac z obrazu dynamodb dostępnego tutaj
- Pobieranie obrazów
docker pull {link do obrazu}
- Listowanie kontenerów
docker ps -a
lubdocker container ls --all
- Startowanie kontenerów
docker start dynamo
- Zatrzymanie kontenera
docker stop dynamo
- Usuwanie kontenera
docker container rm {nazwa/id kontenera}
- Usuwanie wszystkich zatrzymanych kontenerów
docker container prune
docker run -p 8000:8000 amazon/dynamodb-local
Opcja -p
powoduje zbindowanie portu kontenera 8000 na port hosta też 8000
docker run -d --name "dynamo" -p 8000:8000 amazon/dynamodb-local
Po stworzeniu kontenera o nazwie dynamo możemy dostać się do shella bazy danych w przeglądarce wpisując
localhost:8000/shell
Nalezy clonowac z gita
https://github.com/lodz-university-of-technology-masi/SaverS.git
W IntelliJ zaimportować projekt i naciśnąć PPM SaversAPI/build.gradle
i wybrać Import as Gradle Project
Należy mieć skonfigurowany AWS Toolkit i wybrany odpowiedni profil inaczej może się NIE ZBUDOWAĆ
Dla początkowej lambdy wybrać
- From template -> wybrać
template.yaml
a tamHello Function
- Runtime
java8
- Input, plik json
events/event.json
Handler powinnien być w tym przypadku saversapi.App::handleRequest
This project contains source code and supporting files for a serverless application that you can deploy with the SAM CLI. It includes the following files and folders.
- SaversAPI/src/main - Code for the application's Lambda function.
- events - Invocation events that you can use to invoke the function.
- SaversAPI/src/test - Unit tests for the application code.
- template.yaml - A template that defines the application's AWS resources. <- Muy importante
The application uses several AWS resources, including Lambda functions and an API Gateway API. These resources are defined in the template.yaml
file in this project. You can update the template to add AWS resources through the same deployment process that updates your application code.
If you prefer to use an integrated development environment (IDE) to build and test your application, you can use the AWS Toolkit.
The AWS Toolkit is an open source plug-in for popular IDEs that uses the SAM CLI to build and deploy serverless applications on AWS. The AWS Toolkit also adds a simplified step-through debugging experience for Lambda function code. See the following links to get started.
The Serverless Application Model Command Line Interface (SAM CLI) is an extension of the AWS CLI that adds functionality for building and testing Lambda applications. It uses Docker to run your functions in an Amazon Linux environment that matches Lambda. It can also emulate your application's build environment and API.
To use the SAM CLI, you need the following tools.
- AWS CLI - Install the AWS CLI and [configure it with your AWS credentials].
- SAM CLI - Install the SAM CLI
- Java8 - Install the Java SE Development Kit 8
- Docker - Install Docker community edition
The SAM CLI uses an Amazon S3 bucket to store your application's deployment artifacts. If you don't have a bucket suitable for this purpose, create one. Replace BUCKET_NAME
in the commands in this section with a unique bucket name.
AWS$ aws s3 mb s3://BUCKET_NAME
To prepare the application for deployment, use the sam package
command.
AWS$ sam package \
--output-template-file packaged.yaml \
--s3-bucket BUCKET_NAME
The SAM CLI creates deployment packages, uploads them to the S3 bucket, and creates a new version of the template that refers to the artifacts in the bucket.
To deploy the application, use the sam deploy
command.
AWS$ sam deploy \
--template-file packaged.yaml \
--stack-name AWS \
--capabilities CAPABILITY_IAM
After deployment is complete you can run the following command to retrieve the API Gateway Endpoint URL:
AWS$ aws cloudformation describe-stacks \
--stack-name AWS \
--query 'Stacks[].Outputs[?OutputKey==`HelloWorldApi`]' \
--output table
Build your application with the sam build
command.
AWS$ sam build
The SAM CLI installs dependencies defined in SaversAPI/build.gradle
, creates a deployment package, and saves it in the .aws-sam/build
folder.
Test a single function by invoking it directly with a test event. An event is a JSON document that represents the input that the function receives from the event source. Test events are included in the events
folder in this project.
Run functions locally and invoke them with the sam local invoke
command.
AWS$ sam local invoke HelloFunction --event events/event.json
Jezeli wszystko zrobione poprawnie powinno zwrócić taki json
{"body":"{ \"message\": \"hello world\", \"location\": \"ip-number\" }","headers":{"X-Custom-Header":"application/json","Content-Type":"application/json"},"statusCode":200}
The SAM CLI can also emulate your application's API. Use the sam local start-api
to run the API locally on port 3000.
AWS$ sam local start-api
AWS$ curl http://localhost:3000/
The SAM CLI reads the application template to determine the API's routes and the functions that they invoke. The Events
property on each function's definition includes the route and method for each path.
Events:
HelloWorld:
Type: Api
Properties:
Path: /hello
Method: get
The application template uses AWS Serverless Application Model (AWS SAM) to define application resources. AWS SAM is an extension of AWS CloudFormation with a simpler syntax for configuring common serverless application resources such as functions, triggers, and APIs. For resources not included in the SAM specification, you can use standard AWS CloudFormation resource types.
To simplify troubleshooting, SAM CLI has a command called sam logs
. sam logs
lets you fetch logs generated by your deployed Lambda function from the command line. In addition to printing the logs on the terminal, this command has several nifty features to help you quickly find the bug.
NOTE
: This command works for all AWS Lambda functions; not just the ones you deploy using SAM.
AWS$ sam logs -n HelloFunction --stack-name AWS --tail
You can find more information and examples about filtering Lambda function logs in the SAM CLI Documentation.
Tests are defined in the SaversAPI/src/test
folder in this project.
AWS$ cd SaversAPI
SaversAPI$ gradle test
To delete the sample application and the bucket that you created, use the AWS CLI.
AWS$ aws cloudformation delete-stack --stack-name AWS
AWS$ aws s3 rb s3://BUCKET_NAME
See the AWS SAM developer guide for an introduction to SAM specification, the SAM CLI, and serverless application concepts.
Next, you can use AWS Serverless Application Repository to deploy ready to use Apps that go beyond hello world samples and learn how authors developed their applications: AWS Serverless Application Repository main page