This project contains source code and supporting files for the serverless IoT application described at : https://dev.to/pubudusj/how-i-created-a-physical-alarm-to-warn-me-when-my-servers-are-down-gmk.
To use the SAM CLI, you need the following tools.
To build and deploy your application for the first time, run the following in your shell:
sam build --use-container sam deploy --guided
The first command will build the source of your application. The second command will package and deploy your application to AWS, with a series of prompts:
- Stack Name: The name of the stack to deploy to CloudFormation. This should be unique to your account and region, and a good starting point would be something matching your project name.
- AWS Region: The AWS region you want to deploy your app to.
- Confirm changes before deploy: If set to yes, any change sets will be shown to you before execution for manual review. If set to no, the AWS SAM CLI will automatically deploy application changes.
- Allow SAM CLI IAM role creation: Many AWS SAM templates, including this example, create AWS IAM roles required for the AWS Lambda function(s) included to access AWS services. By default, these are scoped down to minimum required permissions. To deploy an AWS CloudFormation stack which creates or modified IAM roles, the
capabilitiesmust be provided. If permission isn't provided through this prompt, to deploy this example you must explicitly pass
--capabilities CAPABILITY_IAMto the
- Save arguments to samconfig.toml: If set to yes, your choices will be saved to a configuration file inside the project, so that in the future you can just re-run
sam deploywithout parameters to deploy changes to your application.
- Env variable BuzzerPin: GPIO pin number for buzzer
- Env variable LedPin: GPIO pin number for LED light
To delete the application that you created, use the AWS CLI. Assuming you used your project name for the stack name, you can run the following:
aws cloudformation delete-stack --stack-name iot-alarm