~/opsmere/services/cloud-azure-aws
Cloud (Azure and AWS)
outcome
You know what runs in the cloud, who has access to it and what it costs.
what I do
- A list of what is already in the cloud, and tidy access rights.
- A secure connection between the cloud and your office.
- Cloud servers that are not visible from the internet.
- Cost alerts, so the bill is never a surprise.
- A place for backups outside the company.
What I usually see
The cloud was meant to be simpler and cheaper than a server in the office. In practice, many companies have a few things there that were set up in a hurry. No order in the names, access open to the internet, and a bill that is a little higher every month.
Nobody knows exactly what runs there, who has access, or whether the office connects to the cloud securely.
What I do
I treat the cloud like another office of the company. It needs to be planned just as carefully.
I connect the cloud to your office with a secure link. Staff use the cloud servers as if they were in the office, but the servers themselves are not visible from the internet. I have built a connection like this before. It linked a company’s branches to its head office, and more than 100 people used it every day.
I keep admin access to a minimum. I set up budgets and cost alerts, so the invoice is never a surprise.
In the Amazon cloud I most often keep backups outside the company and manage domains. I have also run automation tools there.
Who it’s for
For businesses that already have something in the cloud and want to get it under control. Also for those still thinking about moving the office server there. The cloud isn’t always the best choice. If a server on site works out cheaper and simpler, I’ll tell you so plainly.
I do cloud work remotely, so I work with businesses anywhere in the EU in the same way. A free audit of servers and network is a good place to start.
technical details
- Azure
- hub-and-spoke network, site-to-site VPN to the office, virtual machines
- Entra ID
- identity, limited admin access
- Costs
- budgets and cost alerts in Azure and AWS
- AWS S3, Route 53
- backups outside the company, domains and DNS
- AWS IAM, EC2
- permissions, servers for automation tools