How Nebulas Managed Cloud Collaborates with Your Internal Team

01

A collaboration model with clear responsibilities

Nebulas Managed Cloud does not impose a single model: it can fully manage the AWS environment, work alongside an existing internal team, or take on specific areas such as migrations, architectural reviews, automation, security, backup, and cost optimization, always with explicit responsibilities between the parties.

02

How operational collaboration is structured

Steps

1. The managed scope is defined: accounts, identities, networks, environments, access, configurations, and protections.
2. Dashboards and alerts gather technical and application signals and connect them to concrete operational actions.
3. Patches, configurations, and recurring activities become versioned, controllable procedures.
4. Interventions, changes, and decisions leave a clear trail shared with the internal team.

03

What is needed before starting the collaboration

Prerequisites

• Clarity on the scope to be handed over: full environment, side-by-side support, or specific interventions.
• Criteria for data criticality to size retention policies and protected copies.
• Dashboards and alerts set up to gather technical and application signals and connect them to operational actions.
• Explicit responsibilities defined between the internal team and Nebulas for the assigned scope.

04

A hypothetical case of collaboration

Hypothesis: an internal IT department manages daily applications, while Nebulas Managed Cloud handles security, backup, and cost review. The two teams share dashboards and alerts, so technical and application signals reach both, and corrective actions remain traceable and understandable for those who need to act.

05

Checks that keep the collaboration solid

• Restore tests sized to data criticality, not generic ones.
• Repeatable checks on security and compliance of the managed environment.
• Periodic review of consumption and capacity to identify savings opportunities.
• A clear trail of every intervention, change, and shared decision.

06

What a company can configure with Nebulas

A company can define with Nebulas which scope to hand over - full management, side-by-side support, or intervention in specific areas such as migrations and security - and establish explicit responsibilities between its own team and the provider. Choices about who oversees dashboards, alerts, and versioned procedures remain operational options to be agreed upon, not predefined defaults.

07

Practical steps to set up the collaboration

Steps

1. List the technical areas (accounts, networks, access, backup) and assign each to internal or external teams.
2. Set up dashboards and alerts to gather technical and application signals.
3. Define data criticality criteria to size retention and restore.
4. Turn patches, configurations, and recurring activities into versioned, controllable procedures.
5. Schedule periodic reviews of consumption, capacity, and costs with both parties.

08

Next step

If the internal team wants to evaluate a side-by-side or specific intervention model for security, backup, or costs, the first step is to jointly define the scope and shared responsibilities.