bored-oyster-314707/01/2021, 9:12 PM
swift-painter-3108407/01/2021, 9:55 PM
and stops at
or something else?
brash-area-4072907/02/2021, 6:06 AM
resources and the pricing model (0.18 USD/resource-month) does not work at all for us, as much as we would like to take advantage of unlimited stacks.
Our Docker containers and Lambda functions don't care about the number of files involved, so I don't think our frontend builds on S3 should be any different. Has anybody developed a good solution for an S3FolderSync custom resource or similar?
steep-sunset-8939607/05/2021, 2:33 AM
brash-area-4072907/05/2021, 2:37 AM
busy-honey-7381107/05/2021, 7:15 AM
resource it is neither a business object nor a billable AWS resource, it's just an abstraction used to decouple AWS IAM
and AWS IAM
resource from each other. But now in Pulumi it will become a billable resource which is absolutely ridiculous.
• If I create a resource (e.g. a S3 Bucket), Pulumi only provides added value whenever I need to change something on that resource's configuration. Pulumi does not provide any added-value by just storing the resource's state in-between resource modifications. So paying per resource-hour is not usage-based-pricing. Paying per resource modification/operation (e.g. create/update/delete would be usage-based-pricing in this case).
• I have to pay an hourly fee to the cloud provider (e.g. to AWS per EKS control plane hour, or per EC2 instance hour), which is justified as I get an added-value in return (a running EKS cluster resp. a running virtual machine), but having to pay an hourly fee for all the Pulumi micro-resources that make up an EKS cluster or an EC2 instance is just not justified I do not get any added-value in return on an hourly base from Pulumi (as mentioned above Pulumi only provides added-value during configuration change).
I's really sad to see how more and more startups miss the point of their own added-value propositions and just try to imitate business model (pricing) of other players without realising that is does not make any sense at all. That said, it would be totally fine to increase pricing in the existing (old) model if margines are not working out, customers will understand and accept it as long as they still benefit (have an added-value from using Pulumi).
I could go-on with more arguments like this, but now I rather invest my time to figure out what's the impact on my Pulumi bills and if necessary how to move-out of Pulumi again 😞.
bored-oyster-314707/05/2021, 1:05 PM
astonishing-quill-8880707/08/2021, 3:36 PM
gentle-diamond-7014707/08/2021, 8:16 PM
will print your stack summary, with the number of resource for each stack. Repeat that for each bucket/backend you use if you separate them across different buckets (e.g. prod vs. nonprod). Then can take the total number of resources multiplied by 730 (number of hours in a month) to get the Pulumi Credit number for the month.
pulumi stack ls -a
astonishing-quill-8880707/08/2021, 8:17 PM
brash-area-4072907/08/2021, 11:31 PM
). With some creative `--exclude`/`--include` usage, I was able to get the same Cache-Control setup as before
aws s3 sync