It seems like we need to have to copies of the .tf file. One with the endpoints pointing to local stack and one without so it can communicate with aws. Is there a way to make it easier to combine the two .tf files so the transition from testing to deployment is easier ?
Couple questions: 1) does this account for things like an account’s reserved concurrency limit? , 2) does this actually return errors, say your tfstate is out of sync and you try to create a resource that already exists, will it catch that? 3) Say you misconfigured a permission, such as a lambdas ability to access a db, I imagine this won’t catch errors like that, correct? 4) What is the difference between just running terraform plan instead of using local stack?
Thanks for the explanations and demo. I just have one question, how does this work with sdks like the go-sdk-v2? Do we still have to create mock interfaces in go code?
Thanks for introducing the LocalStack, it sounds helpful. I wanted to test the Cloud Formation Scripts locally before I can apply them in AWS directly. Does this help ?
LocalStack is useful for hands-on practice with AWS services when preparing for AWS certifications, as it allows you to interact with mock versions of various AWS services like S3, EC2, and Lambda locally, without incurring any costs. However, it's not a complete substitute for the AWS environment. LocalStack might not support some advanced features and newer AWS services, and there can be differences in service behavior. For comprehensive AWS certification preparation, you should also use AWS's documentation, the AWS Free Tier for real-world experience, and other study materials to cover theoretical knowledge, best practices, and areas not fully replicated in LocalStack. In essence, while LocalStack is beneficial for practical learning, it should be complemented with additional resources for a well-rounded preparation.
Although there is not an equivalent of LocalStack for Azure, Microsoft publish three emulators you can run locally to help with integration testing: 1. Azure Function Core Tools 2. Azure Storage Emulator 3. Cosmos DB Emulator
@@yoitsba so why would anyone want to run localstack if it's not going to let a user test codes in a VM? i mean, what is the point of mimicking the frontend of AWS then?
@@souravsaha3580 I’m assuming it is just for testing your infrastructure deployment with no risk. Idk if it makes any sense to use if that’s the case. I could be wrong
It seems that it doesn't work if you don't have an AWS_API_KEY even with localstack it will ask for credentials so with no access to real aws it seems not working, that's what I am facing
We had no issues using it without a key. Can you try provided in the access and secret key but leave the values to an empty string: "" and see if that works
Great. What if we actually want to plug some back end behind the API? Like - creating a folder somewhere for an S3 bucket. - kicking off a VM with our AMI for an EC2 instance... - or even ckick off a local "EKS Anywhere" instance. Does Localstack support this? You know like a plugin architecture stuff. With community contribs. It should really. That's the first idea any geek would have.
The video was great, but missed some crucial parts (explained in a separate comment above). LocalStack does work with an actual backend behind all AWS APIs and it would be pretty easy to emulate all your examples (we do that for our customers regularly). LocalStack is a commercial open-source project, and while we do get community contributions, we do have our own engineering team working on improving the APIs and adding emulation layers for new AWS services. Internally, LocalStack follows a plugin architecture (powered by our own framework called Plux), and this gives additional features like LocalStack Extensions. You can use the Extension mechanism to further extend LocalStack, and add support for new cloud providers. We recently shipped Cloudflare Workers support with LocalStack through the Extension mechanism :)
LocalStack is a tool designed to emulate various AWS services for local development and testing purposes. So the answer is no. Hopefully, we can have this feature in the future.
🚀Explore Our Top Courses & Special Offers: kode.wiki/40SkWyU
All these tools are overwhelming
that’s why devops is so massive
Thanks Sanjeev
Keep learning with us .Stay connected with our channel and team :) . Do subscribe the channel for more updates : )
Mind-blowing perfect for home labs.
Glad you think so!
Waiting for this video. Thanks for doing this video
Hope you enjoyed it!
Man You Are Good at explaing things just CLICKED SUBSCRIBED!!!!
It seems like we need to have to copies of the .tf file. One with the endpoints pointing to local stack and one without so it can communicate with aws. Is there a way to make it easier to combine the two .tf files so the transition from testing to deployment is easier ?
That's just awesome 😎👍
Thank you! Cheers!
Couple questions: 1) does this account for things like an account’s reserved concurrency limit? , 2) does this actually return errors, say your tfstate is out of sync and you try to create a resource that already exists, will it catch that? 3) Say you misconfigured a permission, such as a lambdas ability to access a db, I imagine this won’t catch errors like that, correct? 4) What is the difference between just running terraform plan instead of using local stack?
Thanks for the explanations and demo. I just have one question, how does this work with sdks like the go-sdk-v2? Do we still have to create mock interfaces in go code?
You shouldn't have to change anything. It will work the same way as if you were talking to the real aws api.
Thanks for introducing the LocalStack, it sounds helpful. I wanted to test the Cloud Formation Scripts locally before I can apply them in AWS directly. Does this help ?
Yes it does. This is one of the main benefits of using LocalStack.
how can you simply display a page using this ec2 like nginx on port 80 to see a sample page?
To what extend can I use LocalStack to practice for my AWS Certifications?
You can use it since its a local cloud sandbox that closely emulates the real AWS environment.
LocalStack is useful for hands-on practice with AWS services when preparing for AWS certifications, as it allows you to interact with mock versions of various AWS services like S3, EC2, and Lambda locally, without incurring any costs. However, it's not a complete substitute for the AWS environment. LocalStack might not support some advanced features and newer AWS services, and there can be differences in service behavior. For comprehensive AWS certification preparation, you should also use AWS's documentation, the AWS Free Tier for real-world experience, and other study materials to cover theoretical knowledge, best practices, and areas not fully replicated in LocalStack. In essence, while LocalStack is beneficial for practical learning, it should be complemented with additional resources for a well-rounded preparation.
How od I use https for endpoint
This video is awesome. So it seems it works only for AWS. Is there any other such tool which works for Azure?
Although there is not an equivalent of LocalStack for Azure, Microsoft publish three emulators you can run locally to help with integration testing:
1. Azure Function Core Tools
2. Azure Storage Emulator
3. Cosmos DB Emulator
Please refer to stackoverflow.com/questions/53888830/local-cloud-stack-for-azure-similar-to-localstack-for-aws
Thanks, does it have a console output?
Yes, it outputs logs to the console, showing the status of the services being started, any errors, and other runtime information
How do I get to know the IP address of the ec2 instance I created? The localstack log does not show it.
Localstack does not create an actual ec2, so there wouldn’t be an IP address I assume
@@yoitsba so why would anyone want to run localstack if it's not going to let a user test codes in a VM? i mean, what is the point of mimicking the frontend of AWS then?
@@souravsaha3580 I’m assuming it is just for testing your infrastructure deployment with no risk. Idk if it makes any sense to use if that’s the case. I could be wrong
It seems that it doesn't work if you don't have an AWS_API_KEY even with localstack it will ask for credentials so with no access to real aws it seems not working, that's what I am facing
We had no issues using it without a key. Can you try provided in the access and secret key but leave the values to an empty string: "" and see if that works
Great. What if we actually want to plug some back end behind the API?
Like
- creating a folder somewhere for an S3 bucket.
- kicking off a VM with our AMI for an EC2 instance...
- or even ckick off a local "EKS Anywhere" instance.
Does Localstack support this? You know like a plugin architecture stuff. With community contribs.
It should really. That's the first idea any geek would have.
The video was great, but missed some crucial parts (explained in a separate comment above). LocalStack does work with an actual backend behind all AWS APIs and it would be pretty easy to emulate all your examples (we do that for our customers regularly). LocalStack is a commercial open-source project, and while we do get community contributions, we do have our own engineering team working on improving the APIs and adding emulation layers for new AWS services. Internally, LocalStack follows a plugin architecture (powered by our own framework called Plux), and this gives additional features like LocalStack Extensions. You can use the Extension mechanism to further extend LocalStack, and add support for new cloud providers. We recently shipped Cloudflare Workers support with LocalStack through the Extension mechanism :)
LocalStack is a tool designed to emulate various AWS services for local development and testing purposes. So the answer is no. Hopefully, we can have this feature in the future.