SShortSingh.
Back to feed

Why Cloud Permission Approvals, Not Installs, Often Delay ROSA Projects

0
·3 views

A ROSA install cannot begin until the customer accepts marketplace terms, which takes only minutes. The larger delay comes from the STS-based installer role, whose elevated trust policy must be reviewed by the customer's cloud security team. On the author's engagements that review took three to five days, with one customer needing nearly two weeks. The fix was a runbook change making identity and permissions approval a required pre-check before any install starts. The article also stresses separating authentication (who is making the request) from authorization (what that identity may do), a distinction that applies equally across AWS, Azure and GCP.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

ZoomEye Scan Finds Thousands of Shopware Instances, Highlighting Admin Exposure Risks

A DEV Community analysis reports ZoomEye search results for the German commerce platform Shopware, showing 2,667 title matches, 1,094 on port 443, and 80 certificate matches as of 23 October 2026. The author notes that a single application fingerprint match suggests web-facing titles and certificates do not reliably reveal the underlying product. The piece argues that commerce admin panels hold sensitive customer data and payment provider credentials, making their exposure the key concern rather than storefront counts. Recommended safeguards include restricting administration access to trusted networks, auditing extensions, and securing staging environments and payment credentials. The analysis also suggests monitoring administrative logins for unfamiliar sources.

0
ProgrammingDEV Community ·

Multi-Tenant Help Center Retrieval: Node.js Design and Three Citation Checks

A developer guide argues that retrieval design for multi-tenant SaaS help centers should prioritize freshness, control, and citation requirements over the choice of vector database. It recommends separating durable indexed content from live lookups, with every answer traced to a tenant-scoped source. The author proposes an ingest, index, query, and cite pipeline, with logging and alerts at each stage so that wrong answers can be traced to a specific step. A small TypeScript validator is presented that confirms every cited chunk was actually returned for the same tenant. The piece also covers trade-offs between re-indexing frequency, latency, and citation stability, and mentions a runtime capability discovery approach tied to a specific API service.

0
ProgrammingDEV Community ·

Solo founder of TalkOctopus weighs open-sourcing its DocSend alternative

The solo founder of TalkOctopus, a platform for sharing documents and tracking engagement similar to DocSend, is considering an open-core model or fully open-sourcing the application. The main goal is to build trust with users. The founder's main concern is losing competitive advantage. The founder has asked for firsthand accounts from others who have open-sourced a SaaS product about what worked well.

0
ProgrammingDEV Community ·

Rebuilding AWS Cloud Skills on Azure: A Week of Lessons in Networking and Cost Control

A developer spent a week recreating familiar AWS architecture concepts on Microsoft Azure, starting with cost-conscious VM sizing and regional capacity limits. Subscription quotas on public IPs and forgotten resources, including an idle Bastion host that bills around $140 monthly, caused unexpected failures and cleanup work. The main project was a three-tier Book Review application with a Next.js frontend, a Node/Express API, and a managed MySQL database, each isolated in its own subnet with NSGs controlling traffic. The author debugged a series of issues, including a mistyped load balancer IP, an unquoted password character read as a comment, and a doubled API path, by testing each network hop in sequence. The week reinforced the value of querying the platform directly and critically reviewing instructions.