# eCloudpod

> Cloud consulting and advisory on AWS and Azure. In cloud since 2017.

The practice is the consulting: what to change, what to leave, and what the consequence will be. Engagements are a review, a platform build, or a retainer. VM start/stop, high availability, FinOps, and an Azure catalog are products used when the advisory calls for them, not the front door.

- Site: https://www.ecloudpod.com/
- Email: info@ecloudpod.com
- Phone: +506 6036 0199
- Based in Costa Rica, remote, with overlap on US Eastern business hours. The account, the repository, and the keys stay with the client.

## How the work is done

The account is already running. A scanner and a diagram do not choose what to change, what to leave, or what happens if the account does not follow the plan. Scope is written before a key is issued. Delivery lands in the client's repository, with a weekly note and a named handoff. A retainer is a separate agreement.

## Services

- AWS consulting. The account you already run: identity, network, the bill, and the pipeline.
- Azure consulting. Landing zones, identity, and a catalog applied by pipeline.
- Cloud architecture advisory. What to change, what to leave, and the consequence.
- DevOps consulting. Environments, CI/CD, and Terraform your team keeps.
- FinOps. Tags, budgets, and waste that can be cut without touching production.
- Observability and SRE. Alerts a person can answer. Scheduled days, not a night desk.
- Cloud security engineering. Findings closed in code. Not a penetration test and not a SOC 2 audit.

## Engagements

- Cost and reliability review. About two weeks. Fixed fee. The bill, the real risks, and a sequenced fix list.
- Platform foundations. Four to eight weeks. Terraform, environments, CI/CD, IAM, secrets, and baseline observability for one product.
- Fractional SRE. Monthly retainer. Scheduled days after the product is live. Not a 24/7 desk.

## Products

- VM start/stop. Each machine has its own window. Non-production stops outside that window. Production is marked always on and stays running.
- High availability for a workload that cannot go down with one failure.
- FinOps: tags, budgets, schedules, and a monthly note.
- Azure self-service catalog applied by pipeline.

## Clouds

AWS and Azure first. Google Cloud, Alibaba Cloud, and DigitalOcean when the system already runs there.