terraform-provider-aws
Portainer
Our great sponsors
terraform-provider-aws | Portainer | |
---|---|---|
99 | 336 | |
9,436 | 28,644 | |
0.9% | 1.5% | |
10.0 | 9.8 | |
6 days ago | 4 days ago | |
Go | TypeScript | |
Mozilla Public License 2.0 | zlib License |
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.
terraform-provider-aws
-
AWS EKS: From IRSA to Pod Identity With Terraform
For Terraform, instead, a new version of the AWS module supports a dedicated resource.
-
Authorization and Amazon Verified Permissions - A New Way to Manage Permissions Part XII: Terraform
If we check the support for the Terraform AWS Provider here (state for the date of publishing this article), we will see that the service is not yet fully supported. Last week, after more than half a year, support for creating a policy store was added. Additionally, we have the configuration to add template policies. However, the identity source is in the form of a PR draft, and there is no PR yet for the ability to create policies.
- 10 Ways for Kubernetes Declarative Configuration Management
-
HashiCorp silently amend Terraform Registry TOS
https://github.com/hashicorp/terraform-provider-aws/issues/3...
The size is what you get when you add every single AWS Go client into one binary.
Each service client like 1-2MB. But when you have 200 services....
-
A Cloud Development Troubleshooting Treasure Hunt
Well, at least we now have a promising lead. Some diligent googling and browsing through Github issues in the AWS provider project yielded no directly related findings. However, I did come across a few recent bug reports about the recent change AWS made regarding the treatment of public buckets. And interestingly, they described precisely the behavior I was encountering.
-
Converting Full Terraform Programs to Pulumi
> We're coming up on 10000 resources in our main Terraform repository and while there is definitely some friction, it's overall much better than having to hit the cloud API's to gather each of those states which would probably take at least an order of magnitude longer.
I don't think that's necessary true. Most cloud API's actually can return hundreds of records with 1 API calls, e.g. https://docs.aws.amazon.com/elasticloadbalancing/latest/APIR... has a maximum page size of 400.
If I manage the cloud resources via some custom tools and/or with some ansible-fu, I can decide to batch the API calls when it makes sense.
With terraform, it is not possible to do so (https://github.com/hashicorp/terraform-plugin-sdk/issues/66, https://github.com/hashicorp/terraform-provider-aws/issues/2...).
-
HEADS UP: Terraform AWS Provider 5.0.0
Release notes - https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0
The only footgun I know of is changing the behavior of RDS instances created from snapshots. Force replacement on snapshot_identifier change for DB cluster resources will fuck up your world if you use a data source for snapshot_identifier since yesterday it would ignore any updates and today it will happily destroy your database (and, because AWS, all of the automated snapshots thereof) when the data identifier changes out from under it. 🎉
-
Any tools out there, or better ways, to unit test IAM policy documents?
A while back I wrote a PR for the AWS provider to expose the policy simulator directly inside Terraform: https://github.com/hashicorp/terraform-provider-aws/pull/25569
-
Weird warning after running pulumi preview
The reason you see that is because the AWS Classic provider (pulumi_aws) is built on top of the open-source terraform-provider-aws (via the Terraform bridge you identified), and terraform-provider-aws is emitting that notice at runtime. Not all Pulumi providers are built from Terraform providers, however, but some, like this one, still are. (There's a notice at the bottom of the page for each resource where this is the case.) It works like this:
Portainer
-
Runtipi: Docker-Based Home Server Management
> Any tips on the minimum hardware or VPS's needed to get a small swarm cluster setup?
From my testing, Docker Swarm is very lightweight, uses less memory than both Hashicorp Nomad and lightweight Kubernetes distros (like K3s). Most of the resource requirements will depend on what containers you actually want to run on the nodes.
You might build a cluster from a bunch of Raspberry Pis, some old OptiPlex boxes or laptops, or whatever you have laying around and it's mostly going to be okay. On a practical level, anything with 1-2 CPU cores and 4 GB of RAM will be okay for running any actually useful software, like a web server/reverse proxy, some databases (PostgreSQL/MySQL/MariaDB), as well as either something for a back end or some pre-packaged software, like Nextcloud.
So, even 5$/month VPSes are more than suitable, even from some of the more cheap hosts like Hetzner or Contabo (though the latter has a bad rep for limited/no support).
That said, you might also want to look at something like Portainer for a nice web based UI, for administering the cluster more easily, it really helps with discoverability and also gives you redeploy web hooks, to make CI easier: https://www.portainer.io/ (works for both Docker Swarm as well as Kubernetes, except the Kubernetes ingress control was a little bit clunky with Traefik instead of Nginx)
- Cómo instalar Docker CLI en Windows sin Docker Desktop y no morir en el intento
-
Docker CI/CD with multiple docker-compose files.
I am currently running Portainer, but webhooks (GitOps) appear to be broken ( [2.19.0] GitOps Updates not automatically polling from git · Issue #10309 · portainer/portainer · GitHub ) and so I cannot send webhook to redeploy a stack. So, looking for alternatives. Using this as a good excuse to learn more about docker and CI/CD etc.
-
Ask HN: How do you manage your “family data warehouse”?
A Synology NAS running Portainer (https://www.portainer.io/) running Paperless NGX (https://github.com/paperless-ngx/paperless-ngx)
This works better than I can possibly tell you.
I have an Epson WorkForce ES-580W that I bought when my mother passed away to bulk scan documents and it scans everything, double-sided if required, multi-page PDFs if required, at very high speed and uploads everything to OneDrive, at which point I drag and drop everything into Paperless.
I could, thinking about it, have the scanner email stuff to Paperless. Might investigate that today.
Paperless will OCR it and make it all searchable. This setup is amazing, I love living in the future.
-
Bare-Metal Kubernetes, Part I: Talos on Hetzner
> I've come to the conclusion (after trying kops, kubespray, kubeadm, kubeone, GKE, EKS) that if you're looking for < 100 node cluster, docker swarm should suffice. Easier to setup, maintain and upgrade.
Personally, I'd also consider throwing Portainer in there, which gives you both a nice way to interact with the cluster, as well as things like webhooks: https://www.portainer.io/
With something like Apache, Nginx, Caddy or something else acting as your "ingress" (taking care of TLS, reverse proxy, headers, rate limits, sometimes mTLS etc.) it's a surprisingly simple setup, at least for simple architectures.
-
What are some of your fav panels and why?
casaos it just makes things like backups, offsite syncing and many other nas related things so much easier to manage. And gives you a proper nas like experience similar to that in which you'd fine on companies like tnas or synology. I actually also use it as a replacement for portainer when i don't need the more advanced features it offers
-
Kubernetes Exposed: One YAML Away from Disaster
> I moved to docker swarm and love it. It's so much easier, straight forward, automatic ingress network and failover were all working out of the box. I'll stay with swarm for now.
I've had decent luck in the past with the K3s distribution, which is a bit cut down Kubernetes: https://k3s.io/
It also integrates nicely with Portainer (aside from occasional Traefik ingress weirdness sometimes), which I already use for Swarm and would suggest to anyone that wants a nice web based UI: https://www.portainer.io/
Others might also mention K0s, MicroK8s or others - there's lots of options there. But even so, I still run Docker Swarm for most of my private stuff as well and it's a breeze.
For my needs, it has just the right amount of abstractions: stacks with services that use networks and can have some storage in the form of volumes or bind mounts. Configuration in the form of environment variables and/or mounted files (or secrets), some deployment constraints and dependencies sometimes, some health checks and restart policies, as well as resource limits.
If I need a mail server, then I just have a container that binds to the ports (even low port numbers) that I need and configure it. If I need a web server, then I can just run Apache/Nginx/Caddy and use more or less 1:1 configuration files that I'd use when setting up either outside of containers, but with the added benefit of being able to refer to other apps by their service names (or aliases, if they have underscores in the names, which sometimes isn't liked).
At a certain scale, it's dead simple to use - no need for PVs and PVCs, no need for Ingress and Service abstractions, or lots and lots of templating that Helm charts would have (although those are nice in other ways).
-
What kind of Alpine user are you?
The control panel is called Homepage. I like it more than Heimdall. To manage Docker I use Portainer.
-
Portainer kind of screwed me after updating a container -- Any other alternatives to managing your containers?
Synology use a custom version of Docker in their NAS products, which we've noted has issues with environment variables. We have this issue open around it, but unfortunately we haven't been able to come up with a fix as of yet and Synology seem to be reluctant to engage with us on it.
-
Risk of self-hosting smaller projects
Here are hundreds of others that did though: https://github.com/portainer/portainer/issues/8452
What are some alternatives?
Yacht - A web interface for managing docker containers with an emphasis on templating to provide 1 click deployments. Think of it like a decentralized app store for servers that anyone can make packages for.
swarmpit - Lightweight mobile-friendly Docker Swarm management UI
podman - Podman: A tool for managing OCI containers and pods.
OpenMediaVault - openmediavault is the next generation network attached storage (NAS) solution based on Debian Linux. Thanks to the modular design of the framework it can be enhanced via plugins. openmediavault is primarily designed to be used in home environments or small home offices.
CasaOS - CasaOS - A simple, easy-to-use, elegant open-source Personal Cloud system.
podman-compose - a script to run docker-compose.yml using podman
octoprint-docker - The dockerized snappy web interface for your 3D printer!
authelia - The Single Sign-On Multi-Factor portal for web apps
Harbor - An open source trusted cloud native registry project that stores, signs, and scans content.
watchtower - A process for automating Docker container base image updates.
Docker Compose - Define and run multi-container applications with Docker
lens - Lens - The way the world runs Kubernetes