It is one of the most consequential questions at exit, and the answer is written in your contract, not in Oracle policy. Many agreements let AWS count only after 365 continuous days. Some exclude public cloud altogether.
By Daniel Voss · Ex Oracle LMS · 4 June 2026
Whether Oracle on AWS counts toward your ULA certification depends on your specific contract. Many agreements allow public cloud deployments to count only if they have run for 365 continuous days at certification. Some exclude public cloud from the baseline entirely, and others are silent, which is not the same as inclusion. Read your cloud clause first, because it decides whether substantial AWS estate becomes permanent entitlement or counts for nothing at exit.
On premises, the rule is straightforward. Oracle deployed within the term, on hardware you control, generally counts toward the certified baseline. Public cloud is different because Oracle treats third party clouds such as AWS and Azure as authorised cloud environments with their own counting rules, and those rules are set in the ULA itself rather than by a universal standard. Two organisations with identical AWS estates can reach opposite outcomes at certification purely because their contracts word the cloud clause differently.
This is why a confident general answer does not exist and should be treated with suspicion. The deployment is the same Oracle software running on the same processors. What changes is whether your agreement chose to let that deployment count, on what conditions, and with what evidence. The work is not to guess what Oracle allows in the abstract but to read what your contract says and plan around it while you still can.
The most common condition in modern ULAs is a continuous running requirement. The clause states that deployments in an authorised public cloud count toward the certification baseline only if they have been running for at least 365 continuous days before the term ends. The logic from Oracle's side is to prevent organisations from spinning up large cloud estates at the last minute purely to inflate the certified number. The effect for you is that timing becomes decisive. A workload that has run in AWS for eighteen months meets the threshold comfortably. A workload stood up four months before exit does not, and may count for nothing even though it is real, in use, and licensed under the unlimited right.
Where this rule applies, the planning implication is clear. Any AWS deployment you intend to count must be in place at least a full year before the term ends, and you need evidence of continuous operation across that period. A measurement taken at the window is not enough on its own. The history matters, because the clause is about duration, and duration has to be proven.
Read the cloud clause before you assume the cloud counts. Silence is not inclusion, a late deployment is not a counting one, and the only safe answer is the one your own contract gives. Plan AWS estate around that wording, not around hope.
Cloud clauses tend to fall into one of three patterns, and the right move at exit is completely different in each. Identifying which one governs your agreement is the first step.
The table below shows how the same AWS estate can reach different outcomes depending on the clause for an anonymized example. The figures are indicative and exist to show the logic, not to represent any real engagement, and the actual outcome depends entirely on the wording of the specific agreement.
| Clause type | AWS processors counted | Why |
|---|---|---|
| Counts, ran over 365 days | 800 | Threshold met and evidenced |
| Counts, deployed late | 0 | Continuous running threshold not met |
| Public cloud excluded | 0 | Repatriate or move to OCI to count |
| Silent clause | To be determined | Resolve before the window |
Indicative only. The outcome for your estate depends entirely on the wording of your cloud clause and on the evidence of continuous operation. Treat this as a map of possibilities, not a prediction.
If your clause excludes public cloud, or your AWS estate will not meet a continuous running threshold in time, the deployments do not have to be lost. Workloads can be repatriated on premises before exit, where they generally count, or moved to Oracle Cloud Infrastructure, which Oracle treats differently from third party clouds. Either route takes time and planning, which is exactly why the cloud clause should be read early rather than discovered at the window. The worst outcome is to learn at the eleventh hour that a large, genuine AWS estate counts for nothing, with no runway left to act.
The AWS question is decided by your contract, and the time to read it is now, while there is still runway to act on what it says. Find your cloud clause, identify which of the three patterns governs it, and plan accordingly. For the full reading method, see auditing your cloud clause before exit, handle the standby case in cloud DR and the certification count, and ground the approach in our ULA exit strategy guide.
Book a ULA assessment and we will read your cloud clause, tell you whether your AWS estate counts, and map the moves that turn cloud deployment into permanent entitlement.