Posts tagged: aws

External Link X (formerly Twitter) · x.com [1] This is a really great animation of latency across different aws regions based on us-east-1. Note This post is a thought [2]. It’s a short note that I make about someone else’s content online #thoughts References: [1]: https://x.com/BenjDicken/status/1963998076198105475 [2]: /thoughts/

External Link medium.com [1] Imagine waking up to a $1,300 for running an example project! That sounds like peanuts for a cloud bill but for an individual trying to learn that hits my monthly budget real hard. That’s what happened to Marciej, make sure you check out the full article and give them a 👏 on Medium if you have an account. The more I see things come out about aws, the more it makes me sick, and confirm my feelings that I cannot possibly use them for a side project without some real $$ planning to come out of it. Yes, S3 charges for unauthorized requests (4xx) as well[1]. That’s expected behavior. They offer no DDOS protection against 4xx or 5xx requests against your bucket. Absolutely bonkers that you have ZERO control over this. --- This response just feels absolutely gross. I notified the AWS security team. I suggested that they restrict the unfortunate S3 bucket name to protect their customers from unexpected charges, and to protect the impacted companies from data leaks. But they were unwilling to address misconfigurations of third-party products. It sounds like this guy followed some default instructions for an example site, HOW MANY OTHERS have done th...

External Link X (formerly Twitter) · twitter.com [1] Wow, shocked at these results. All this time I’ve been told and believed that k8s is incredibly hard, and you need a $1M problem before you think about it because it will take a $1M team to maintain it. So far my experience has been good, and I definitely do not have a $1M problem in my homelab [2]. [1] Note This post is a thought [3]. It’s a short note that I make about someone else’s content online #thoughts References: [1]: https://twitter.com/_WaylonWalker/status/1718300097174270193 [2]: /homelab/ [3]: /thoughts/

Upon first running an aws cli command using localstack you might end up with the following error. Unable to locate credentials. You can configure credentials by running "aws configure". Easy way # [1] The easy easiest way is to leverage a package called awscli-local. pipx install awscli-local Leveraging the awscli # [2] If you want to use the cli pro pipx install awscli aws config --profile localstack # put what you want for the keys, but enter a valid region like us-east-1 alias aws='aws --endpoint-url http://localhost:4566 --profile localstack' References: [1]: #easy-way [2]: #leveraging-the-awscli

I ran into an issue where I was unable to ask localstack for its status. I would run the command and it would tell me that it didn’t have permission to read files from my own home directory. Let’s fix it The issue # [1] I would run this to ask for the status. localstack status And get this error PermissionError: [Errno 13] Permission denied: '/home/waylon/.cache/localstack/image_metadata' What happened # [2] It dawned on me that the first time I ran localstack was straight docker, not the python cli. When docker runs it typically runs as root unless the Dockerfile sets up a user and group for it. [3] How to fix it # [4] If you have sudo access to the machine you are on you can recursively change ownership to your user and group. I chose to just give myself ownership of my whole ~/.cache directory you could choose a deeper directory if you want. I feel pretty safe giving myself ownership to my own cache directory on my own machine. whoami # waylon chown -R waylon:waylon ~/.cache Now it’s working # [5] Running localstack status now gives me a nice status message rather than an error. ❯ localstack status ┌─────────────────┬──────────────────────────────────────────────...