Public sector

AWS for Cities, Departments and Public Entities in Colombia

A services portal that crashes on the last day of the deadline, documents on a server with no backup, and a cloud contract nobody knows how to measure. CloudTing designs, migrates and runs the technical side on AWS, with the traceability internal control asks for and spending in plain sight.

Review my entity's infrastructure Frequently asked questions ↓

What we solve

Online services portals that hold up during deadline peaks
Filed documents in S3, versioned, encrypted and never public
Full traceability: who did what and when, in logs that cannot be deleted
Separate accounts for production, testing and logs, with rules nobody can skip
Budgets and alerts so usage never goes past what was contracted
A disaster recovery plan that has been tested, not just written

Who it is for

Cities and departments that want to move services and files off their own servers
National and decentralized entities that already bought cloud and need someone to design and run it
Utilities with payment and inquiry portals
IT offices that must meet the Digital Government Policy with few people

What applies in Colombia

Colombia Compra Eficiente, the national procurement agency, runs the Public Cloud V Framework Agreement, which started on March 5, 2026 and is in force until March 2028. AWS is in the hyperscale public cloud catalog.
That framework agreement covers cloud and complementary services such as migration, administration and support. Consulting and custom development are excluded and are contracted separately.
Decree 767 of 2022 sets the Digital Government Policy. One of its enablers is information security and privacy: confidentiality, integrity, availability and privacy of data.
Law 1581 of 2012 applies to the citizens' personal data the entity receives through its services.

What we do not do

We do not give legal or public procurement advice, and we are not a supplier under the framework agreement. We handle the technical side (design, migration, operations and evidence) through whatever contracting mechanism your entity chooses; your legal team decides how to buy.

Sources

Reference architecture

A typical pattern for online services: CloudFront with WAF and Shield in front, the portal on ECS Fargate across two zones, case files in encrypted RDS Multi-AZ, documents in S3, notifications through SES, and Control Tower separating production, testing and logs into accounts with rules, with CloudTrail and Config as evidence.

How we start

1Free review: we look at access, encryption, backups, cost and what evidence exists today
2Report with prioritized risks and a proposed AWS architecture
3Migration or fixes in stages, without stopping operations
4A real recovery test, with RPO and RTO measured
5Ongoing operations and support, if you need it

Frequently asked questions

Can a public entity buy AWS through the framework agreement?

Yes. The Public Cloud V Framework Agreement includes AWS in the hyperscale public cloud segment, and the purchase is made in the Colombian State's Virtual Store (TVEC). The Colombia Compra Eficiente buyer's guide explains each step.

And who designs and runs the platform after the cloud is bought?

That is the part we do: architecture, migration, security, backups and operations. Since consulting is excluded from the framework agreement, it is contracted through the mechanism your entity chooses.

How do we show an auditor who did what?

AWS CloudTrail records every action and AWS Config keeps the change history of every resource. Those logs are copied to a separate account locked against deletion, so nobody, not even an administrator, can alter them.

How do we keep usage within what was contracted?

AWS Budgets sends alerts before you reach the contracted amount, and tags show what each project or office spends. That way the contract supervisor sees real usage every month.

Next step

AWS for Cities, Departments and Public Entities in Colombia

Review my entity's infrastructure →See all services