CommPulse

submitted by /u/heldsteel7 to r/FinOps [link] [comments]

submitted by /u/easybits_ai to r/FinOps [link] [comments]

We’re seeing a 300–400% increase in VMware licensing costs. On top of that, recent quotes from Dell are three to four times higher than we would normally expect, especially for memory and storage. Fortunately, we refreshed our storage environment about a year ago and went all-in on Pure Storage as-a-Service, its the only predictable fixed dollar amount subscription at this point, so we don’t have a major SAN lift-and-replace looming. Given today’s pricing, I can only imagine what that would cost now. We’re also in a good position on the compute side. Production is running almost entirely on current-generation Dell R7xx servers, which means we could pause hardware procurement for two or three years and likely remain under active maintenance without much operational risk. That said, simply kicking the can down the road doesn’t feel like a sustainable strategy. We would eventually be facing a large, simultaneous refresh—potentially at even higher hardware and licensing costs. Our on-prem footprint is relatively small: two three-node clusters, each with 192 cores, 4 TB of memory, and 23 TB of low-latency NVMe storage, plus a handful of high-performance, dedicated ERP/database and dedicated backup servers. At this point, I’m genuinely questioning whether continuing to operate our own data center will remain economically viable. What are other on-prem shops doing? Are you maintaining staggered refresh cycles, extending hardware lifespans, moving away from VMware, switching vendors, buying refurbished equipment, or shifting more workloads to the cloud? I also have to assume these increases will eventually ripple through to IaaS pricing from AWS, Azure, and other cloud providers. Those of you in similar situations, how are you approaching this? submitted by /u/-c3rberus- to r/sysadmin [link] [comments]

Built this to run inside our own AWS account which utlizes Redshift, RDS, S3 and Amazon bedrock, and it might be useful to others here. It's one stateless Node container plus a Postgres (Supabase) project. Runs fine on ECS/Fargate, App Runner, EKS, or plain EC2 — /api/health for ALB target-group checks, no sticky sessions, no local state, so it scales horizontally behind an ALB. Background work (scheduled refreshes, syncs) is coordinated through the database with a cross-instance lease, and DISABLE_INPROCESS_SCHEDULER pins it to one task if you'd rather. AWS-relevant bits: Redshift, Athena, RDS/Aurora (Postgres + MySQL) queried read-only in place, with connection pooling Bedrock as a model provider (or OpenAI/Anthropic/OpenRouter/Ollama — your keys, direct from your account, nothing proxied through me) Outbound calls honour HTTPS_PROXY/NO_PROXY for accounts with no direct egress SSRF guard blocks 169.254.169.254 and link-local ranges while deliberately allowing private ranges, so a Redshift cluster in your VPC works but a prompt can't talk the instance metadata endpoint into handing over role credentials Governance: read-only SQL enforcement, RLS on every table, hash-chained audit log, per-user spend caps, full cost traces. Honest bits: needs a Supabase project specifically (Postgres + auth + storage + pgvector — self-hostable, or their free tier), no SOC 2, no pentest report, and it's source-available under Elastic License 2.0, not OSI open source — run it for yourself and your clients, just don't resell it as a hosted service. github.com/AgentSwarms-fyi/agentswarms — happy to talk architecture. submitted by /u/Outside-Risk-8912 to r/aws [link] [comments]

We received an email about PostgreSQL versions 11, 12, and 13 are all going into extended support and costs will increase starting 9/1. There isn't any information on how much more the cost will be. We only have two DB instances running on the affected versions, so hopefully it won't be much of an impact, but does anyone know how to find out pricing for the extended support? I've already spoke with the business unit that uses the database and they can be upgraded eventually just not at the moment. Also, I inherited this environment this week and this was one of the first emails I've received so... good start :) submitted by /u/No_Ring1809 to r/sysadmin [link] [comments]

https://preview.redd.it/xwwdz2ozw9kh1.png?width=1246&format=png&auto=webp&s=f19f1cfadf6e4e48d2f56a0135f3fd5e49011bd1 Today, I passed CKS with 75% (not a good score) and wrote a detailed blog about my exam experience, preparation approach, the resources I used, and the Kubernetes security topics that helped me the most. DMs are open if you are preparing for the exam. I can help with whatever is still fresh in my memory. My biggest takeaway: CKS is noticeably harder than CKAD and CKA. It is not only about knowing Kubernetes commands. You need to understand why a configuration is insecure, how to fix it, and how to verify that your change actually worked. The biggest mistake I made was spending around 10–15 minutes too long on one question because I felt I was close to solving it. That created unnecessary pressure towards the end and probably led to a couple of avoidable mistakes. So my strongest advice is: if you are stuck and don’t see a clear path after a few minutes, mark the question and move on. A few things that helped me: Don’t memorise solutions. Understand the security reasoning behind them. If a NetworkPolicy, API server flag, securityContext, audit policy, or admission control changes slightly, memorised YAML will not help much. Always verify your work. Security changes can easily break workloads or cluster components. Check Pods, control-plane components, logs, services, NetworkPolicy connectivity, admission behaviour, audit logs, node readiness, and systemd services wherever required. Be comfortable with Linux as well as Kubernetes. CKS can require you to work with configuration files, systemd services, container runtimes, permissions, certificates, and node-level settings. Use documentation whenever required instead of trying to remember every flag or custom resource. Topics I would strongly recommend practicing: Kubelet and etcd hardening kube-apiserver authentication and authorization Admission controls and ImagePolicyWebhook Secure Dockerfiles and non-root containers Container immutability and securityContext Audit policies and API server logging NetworkPolicy HTTPS Ingress and TLS ServiceAccount token security Worker node administration and upgrades SBOM and software supply-chain security Restricted Pod Security Standard Docker/container runtime hardening Istio STRICT mTLS Cilium network security CIS benchmarks and kube-bench remediation Resources I used: KodeKloud CKS course KodeKloud Ultimate Mock Exam Series iximiuz Labs KillerKoda Killer.sh CKS simulator ChatGPT/Claude for topics that needed a simpler explanation or extra practice scenarios Between the KodeKloud course mocks and Ultimate Mock Exam Series, I had around six mock exams. I found them very useful and reasonably close to the level of difficulty you should prepare for. Killer.sh felt a little off-track compared with the actual exam in some areas, but I would still recommend doing it. It is useful for practicing under time pressure, discovering knowledge gaps, and improving troubleshooting skills. I also used ChatGPT and Claude quite a lot during preparation. CKS has many small security topics, and sometimes a course or lab explanation may not immediately click. In those cases, asking AI to explain the concept differently, compare configurations, or generate a small practice scenario was very useful. The simplest advice I can give is: practice a lot, understand the security reasoning behind what you are doing, verify every change, and don’t let one difficult question consume your exam time. I also wrote a full blog with more details on my preparation strategy, resources, task areas, mistakes, and lessons from the exam. Blog: https://blog.prateekjain.dev/cks-exam-experience-2026-preparation-strategy-and-lessons-learned-1fad785a430b?sk=52b58a9c6d812444bc1340f15eda7dd6 submitted by /u/root0ps to r/devops [link] [comments]

submitted by /u/HiHiRedditUser to r/FinOps [link] [comments]

submitted by /u/codingdecently to r/FinOps [link] [comments]

when you've started rotating a credential and then discovered it was already revoked, or was never a real key in the first place — roughly how long had you burned before you worked that out? minutes, or did someone spend an hour convinced they were looking in the wrong project? submitted by /u/grishma_1503 to r/devops [link] [comments]

Company is thinking about getting onboard the AI train exploring options. What are some questions that should be answered throughout the review process and things to know going forward when implementation is complete? submitted by /u/Pope_Carl_LXIX to r/FinOps [link] [comments]

Recently we tried to cut the model price on an internal research agent and it barely moved the needle. We initially had the obvious theory that the expensive model caused the spend. When we then looked at cost per successful task instead of cost per model call we saw something different. A large chunk of the sessions called search repeatedly, pulled nearly identical results, and stuffed every tool output back into context. Some heavy sessions were legitimate. Complex research really did need multiple searches and a larger model. Others were just retry loops caused by weak stopping conditions, bad tool arguments, or the model missing that the previous result already answered the question. The cheaper model occasionally made that worse by needing more attempts. We used Braintrust to break down token counts, latency, cost and tool-call patterns by trace. That gave product, engineering and finance the same unit of analysis, a completed task rather than a single API request. We added loop detection and deduplicated tool outputs then routed simple requests to the smaller model and compared the change against the same eval set. What we saw was fewer repeated calls which drove more savings than the model swap and answer quality held. Latency improved too because the agent stopped arguing with the search endpoint five times. How are people measuring agent cost when retries and tool loops make per-call metrics basically meaningless? submitted by /u/Slight_Piccolo_3746 to r/googlecloud [link] [comments]

Small business. Not a huge budget, especially not given the economic situation. We run Meraki MX devices at a number of offices. We also have a number of creative users that work from home and need fast + resilient tunnels to navigate and transfer files quickly. Semi-recently Meraki began offering IKEv2/IPSEC. Works great, super fast. Problem is, they don't have MFA support for it yet. They seem to want you to use AnyConnect Premium, but the Meraki only supports TLS/DTLS tunnel type, which is substantially slower for transferring large files. They also don't support client certificate validation for IKEv2/IPsec, which would be another good option that isn't "anyone with a username/password who knows the termination IP/name can connect." Right now we authenticate by pointing the MXs at an NPS server in Azure, which is joined to an Entra DS domain. We want to avoid managing an AD domain but are heavily integrated into the MS ecosystem (Teams, Office, Win11 Business, Intune, etc). Is there a tool or service that we could point the MX's RADIUS server field at, that integrates with Entra/Entra DS that could perform MFA on its end before returning success and granting access, augmenting the basic username/password auth? submitted by /u/VaporousMote to r/sysadmin [link] [comments]

Two weeks ago I posted my concerns about the long term viability of using Gemini in my automated content moderation app. We covered the option of alternate models there so please constrain this discussion to what appears to be sneaky policy settings to extract more revenue from Gemini users. When 2.5-flash-lite is deprecated my costs will be 16x on 3.1-flash-lite but actually it will be more than that because on the 3 series models you can't disable thinking nor specify temperature, top_p and top_k. Of those I only know a little about temperature which I have set set to 0.1 for my purposes. From 3.1 onward the best I will be able to do is specify a "LOW" thinking level which will burn at least some additional tokens and might break my app because having the model act deterministically is essential for content moderation purposes. Sure I could add additional system instructions to try and compensate for this loss of control but up go my input costs. Granted you can still specify maxOutputTokens but if that value is too low to account for the mandatory "thinking" the call will fail is that right? So we're going from a situation where you can tightly control the cost of each call to the LLM to one where you're at the mercy of the model. As I mentioned above I think this policy is sneaky which would be entirely consistent Google's opaque cloud billing and costs in general. Alternatively these changes are just where the rubber meets the road? submitted by /u/dougception to r/googlecloud [link] [comments]

I was in the process of creating an Azure SQL Managed Instance for our CIS dept (I work at a College). The cost estimate came out to $1,400/month - which is too much. Any way around that? submitted by /u/Real-Patriot-1128 to r/AZURE [link] [comments]

Last update August 14, 2026 at 8:29am PDT Description At 8/14/2026 7:35 AM PT, the Core Identity team became aware of an issue with email deliverability affecting customers in commercial cells. During this time, users may be experiencing intermittent issues receiving email from Okta. Our team is actively investigating this issue and is working to mitigate it. 8:39am PDT: Okta Engineering has determined that certain third-party providers were failing to receive emails from Okta. Our monitoring shows delivery rates are recovering to normal conditions and will continue to monitor until full resolution. Our next update will be in 30 minutes or sooner if additional information becomes available. 8:23am PDT: Okta Engineering is investigating and has determined that the incident is currently impacting email delivery to a subset of customers. During this time, customers may experience email delivery deferrals. We’ll provide an update in 30 minutes, or sooner if additional information becomes available. https://status.okta.com/#incident/a9CWR0000002FZG2A2 submitted by /u/BB03440 to r/sysadmin [link] [comments]

[ Removed by Reddit on account of violating the content policy . ] submitted by /u/cloudquell123 to r/FinOps [link] [comments]

When I talk to analytics leaders, the #1 thing they complain about is data debt. They assume their pipelines are fundamentally broken and that the only fix is a six-figure, multi-month overhaul of their cloud stack. Usually, that’s completely wrong. The problem isn't that data debt exists—every scaling company accumulates it as a natural byproduct of growth. The real problem is that their data debt is completely hidden in the dark . When data debt lives in the dark: Executives sit in 9:30 AM daily syncs arguing over spreadsheet semantics and metric definitions instead of making strategic decisions. Stakeholders treat the analytics team like a fast-food drive-thru, shouting isolated data requests into the microphone without context. Analysts waste 80% of their bandwidth acting as "data detectives" trying to trace broken C-suite CSV exports. At U&I Consulting , we don't promise to magically erase data debt overnight. Instead, we illuminate it . We bring hidden operational pipeline deficiencies into the light using Data Debt Diagnostics and formal Data Debt Tickets . When you quantify data debt and map it visually, it transforms from an invisible bottleneck into a clear, business-justified roadmap for the executive team. By combining this with Agile Ledger Architecture (ALA) , Medallion Pipelines (Bronze/Silver/Gold) , and KPI Shields , you protect team bandwidth and accelerate executive Time to Insight (TTI) . Stop trying to pretend data debt doesn't exist. Illuminate it, quantify it, and build an architecture that lets your business scale past it. 📖 Detailed in my book, "WHERE ARE THE INSIGHTS? The Blueprint for Agile Ledger Architecture" 🌐 Advisory & Diagnostics: uiconsulting.com submitted by /u/ui-consulting to r/FinOps [link] [comments]

Hello So i will be quick i want to ask some questions which are -------------------------------------------------------------------------- 1- I am a complete begineer who knows nothing so how can i learn finops like what things or tools or softwares would i need to learn communications and other skills or are tools enough -------------------------------------------------------------------------- 2- Is a FinOps a smart move right now for somone who doesn't have any experience with cloud but is willing to learn also are finding jobs preferably easy and how much can you expect 3- Is a fully remote job possible -------------------------------------------------------------------------- 4-Would it be a good option right now as compared to other options -------------------------------------------------------------------------- i had other questions which i wanted to ask but remember so will ask them at a later time submitted by /u/simply_complexiyo to r/FinOps [link] [comments]

Anybody here who feels AI SRE is a gimmick? I mean, what are we doing with this, honestly? Not gonna name names, but our observability platform ships one, and it takes 10–12 minutes to run an incident analysis and comes back with "hey, these are 2 things that are broken, and these are 5 probable causes." In the last three incidents, the causes it flagged were real issues acting up as bugs, but not related to the current incident at all. So I'm getting a faster RCA, just a wrong one. I raise a ticket and get misleading suggestions. Just to get an unbiased opinion, I tried out a few other names on the market: similar results. Happy to hear if anyone has had a different experience. submitted by /u/Less_Ad8195 to r/devops [link] [comments]

We're seeing issues with Ubuntu clients (22.04/24.04/26.04) failing to check in with Intune since thursday. Intune logs on the clients say "Failed to Check in with Intune. Failed to update device inventory. <some MS URL> Status Code 500". Some other logs also say 400 or 404. Latest version of intune-portal and microsoft-identity-broker installed. Downgrade did not help. Trying to enroll a new device will either: result in the device only landing in Entra, but not in Intune result in the device appearing in both Entra and Intune, but without any inventory data Entra shows "Ubuntu+26.04+LTS" as OS version, while Intune shows either nothing (blank) or "0.0.0.0", resulting in the device not picking up our compliance policy -> device will be not compliant -> user cant login to M365 apps. dsreg on the client shows that it correctly registered to Entra. Trying to trigger a sync or log in locally in the Intune portal app will immediately result in an error message ("Device could not be registered. There was an error, please try again"). Existing clients that are already enrolled also fail checkin and logon on the Intune portal app. But since they're still compliant users can still log in to M365 apps. There seems to be an issue going on at Microsoft's side. There's an open issue in the admin center (OP1459987), which sounds like it might be related giving the intune-portal app fails to update its device inventory. "Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center" submitted by /u/EpicSimon to r/sysadmin [link] [comments]