cloudformation-templates
LocalStack
| cloudformation-templates | LocalStack | |
|---|---|---|
| 1 | 154 | |
| 0 | 52,289 | |
| - | 0.8% | |
| 0.0 | 9.9 | |
| about 2 years ago | about 17 hours ago | |
| Python | Python | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cloudformation-templates
-
Hello, I used the free version of every instance I used (free tier), but I was surprised that I have to pay for the database, I deleted everything I could find running in my account, but the fee is still there, is there a way to remove this fee or at least prevent it from happening again?
Set up billing alarms, it's what I do the first thing with any new AWS account (that, and setting up MFA!). Cloudformation template example here which creates a billing alarm.
LocalStack
- LocalStack – a functional local AWS cloud stack
-
Let's build a screenshot API
Later you can use any S3 compatible storage because the code I write will still work, but for testing purposes on my local machine, I will use LocalStack:
-
LocalStack e AWS CLI: Como desenvolver localmente com a AWS
Acesse o site da LocalStack e faça login.
-
Cutting down AWS cost by $150k per year simply by shutting things off
To give this a slightly different spin:
--> "The best optimization is simply not spinning things up."
At least for local development and testing, as made possible by LocalStack (https://localstack.cloud), among other local testing solutions and emulators.
We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS".
What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place.
-
Getting Amazonka S3 to work with localstack
(For others who hadn't heard of it: localstack is
- LocalStack v3.0.0
- Localstack, a "AWS" local para desenvolvimento em cloud
-
Integration tests with AWS S3 buckets using Localstack and Testcontainers
LocalStack Website
- LocalStack: A functional local AWS cloud stack
-
Simulando a AWS no seu ambiente Local
O Localstack: https://localstack.cloud/, é um recurso que possibilita simular diversos recursos AWS (dynamoDB, s3, iam, cognito, ses), dentro da sua máquina, utilizando o docker.
What are some alternatives?
serverless-micro-django - Lightweight yet powerful python utility for lambda functions, Use Django ORM in your Python lambda functions
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
aws-lambda-chaos-injection - Chaos Injection library for AWS Lambda
sst - Build modern full-stack applications on AWS
cloud-nuke - A tool for cleaning up your cloud accounts by nuking (deleting) all resources within it
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
ssl-check-api - This api returns the ssl expiration date of the hostname.
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
aws-secrets-manager-rotation-lambdas - Contains Lambda functions to be used for automatic rotation of secrets stored in AWS Secrets Manager
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
Appwrite - Your backend, minus the hassle.
testcontainers-python - Testcontainers is a Python library that providing a friendly API to run Docker container. It is designed to create runtime environment to use during your automatic tests.