# uae Published articles for uae. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Satellite-derived bathymetry of Arabian Gulf ports under leakage-free validation: a multi-site benchmark of empirical, machine-learning and deep-learning models against 285,000 multibeam soundings, with an outlook for UAE waters DevFeed: [Satellite-derived bathymetry of Arabian Gulf ports under leakage-free validation: a multi-site benchmark of empirical, machine-learning and deep-learning models against 285,000 multibeam soundings, with an outlook for UAE waters]() Original publisher: [Read original article]() Author: Muhammad Saeed, Mohamed H. Alhosani, Dmitry Mikhaylov, Yasser F. Al Wahedi Published: 2026-11-02T05:00:00Z Content type: article Language: en Sources: [arXiv: Machine Learning]() Topics: [Machine learning]() Tags: [benchmark](), [blocks](), [change](), [control](), [cost](), [cs-cv](), [cs-lg](), [deep-learning](), [gulf](), [machine-learning](), [models](), [monitoring](), [order](), [physics-ao-ph](), [physics-geo-ph](), [reconnaissance](), [satellite](), [site](), [split](), [survey](), [uae](), [validation]() ### AI overview Across six Abu Dhabi port areas, validation design affected satellite-derived bathymetry accuracy more than model choice: LightGBM RMSE rose from 0.57 m on random pixel splits to 1.30 m on spatial blocks and 1.66 m at an unseen site. At that unseen site, the Stumpf ratio (1.45 m) outperformed LightGBM, U-Net and Lyzenga. With about 20% local control soundings, a hybrid of tree output and band ratio achieved 1.11 m RMSE over 0-11 m, with 67% of pixels within IHO S-44 Order 2 tolerance; the seabed was not readable beyond 11 m. A 60 m UAE coastal reconnaissance mosaic calibrated with ICESat-2, without vessel survey data, reached 1.42 m RMSE on held-out blocks over half the product. The abstract concludes that Sentinel-2 SDB with roughly 100 control depths per image can support reconnaissance and change monitoring to about 10 m, but does not meet S-44 Order 1 without local control; random-split accuracy should not be treated as operational accuracy. ### Source excerpt arXiv:2610.33609v2 Announce Type: replace Abstract: Satellite-derived bathymetry (SDB) is often proposed as a low-cost complement to multibeam surveys of ports, but its accuracy is seldom measured on an area the model has never seen. We test SDB in the turbid, shallow and tidal waters of the Abu Dhabi coast against 285,619 multibeam soundings from twelve surveys at six port areas, reduced to Lowest Astronomical Tide. The Stumpf ratio, the Lyzenga transform, a monotonic gradient-boosted tree model (LightGBM) and a U-Net ensemble were trained on 72 Sentinel-2 images and tested in transfer to an unseen site and with local control (about 20% of a site's soundings, spatial blocks beyond a 225 m buffer). The validation design changed the result more than the model: the same LightGBM model gave 0.57 m RMSE under a random pixel split, 1.30 m under spatial blocks and 1.66 m at an unseen site. In transfer the Stumpf ratio (1.45 m) was not beaten by LightGBM, the U-Net or Lyzenga. With local control a hybrid of the tree output and the band ratio reached 1.11 m over 0-11 m, 67% of pixels within the IHO S-44 Order 2 tolerance and a conformal 95% interval with 95% observed coverage; in clear water it reached 0.29-0.53 m. The seabed could not be read beyond 11 m, and summer images were five to six times more turbid than winter ones. ICESat-2 ATL24 agreed with the surveys to 0.25 m after a depth-dependent offset was removed. A 60 m reconnaissance mosaic of 17,200 km2 of the UAE coast, calibrated cell by cell on ICESat-2 without any vessel survey, reached 1.42 m RMSE on held-out blocks over half of the product. Sentinel-2 SDB with about a hundred control depths per image is a usable reconnaissance and change-monitoring tool in these waters to about 10 m; it does not meet S-44 Order 1 without local control, and accuracies from random splits should not be taken as operational accuracy. ## AWS cloud region damage in Bahrain and the UAE exposes disaster recovery limits DevFeed: [AWS cloud region damage in Bahrain and the UAE exposes disaster recovery limits]() Original publisher: [Read original article]() Author: David Linthicum Published: 2026-09-29T09:00:00Z Content type: opinion Language: en Sources: [InfoWorld]() Topics: [Disaster Recovery](), [Amazon Web Services](), [Cloud](), [cloud-infrastructure]() Tags: [amazon-web-services](), [availability](), [business-continuity](), [business-continuity-cloud-computing-iaas-saas-security](), [cloud](), [cloud-computing](), [iaas](), [infrastructure](), [iran](), [israel](), [middle-east](), [military](), [saas](), [security](), [uae](), [us](), [war]() ### AI overview Physical damage from strikes left AWS unable to restore access to its Bahrain region and a UAE availability zone, with restoration updates expected months later or in early 2027. The article argues that the incident challenges assumptions about independent availability zones and highlights the risk to data and workloads that were not migrated elsewhere. ### Source excerpt I've covered cloud computing for a long time, and one of the most persistent myths I encounter is that public clouds exist above the laws of physics that govern everything else in technology. The events coming out of the Middle East should put that myth to rest for good. Reuters reported this week that Amazon Web Services says it cannot restore access to its cloud region in Bahrain and to one of its three data-hosting zones in the United Arab Emirates, following damage during the Iran war. The status update is stark reading. AWS admitted that the damage in Bahrain spanned multiple availability zones (AZs) and, in its own words, "exceeded what our regional and multi-AZ services are designed to withstand." Think about that for a moment. The entire architectural premise of availability zones is that they fail independently, so a multi-AZ deployment survives a localized disaster. The war destroyed that assumption in a single stroke. The disruptions began in March, after US and Israeli attacks on Iran prompted Tehran to retaliate with missile and drone strikes on Israel and on Gulf states hosting US military bases. Two of AWS's facilities in the UAE were directly struck, and a drone strike close to a Bahrain facility physically damaged infrastructure there. A second Bahrain availability zone went down in April, and the region became effectively unavailable. In the UAE, AWS says it cannot restore resources and data hosted exclusively in the zone known as mec1-az2. The company has notified authorities in both countries and is helping customers re-establish operations in other regions. AWS expects to provide a UAE restoration update in the coming months, with a Bahrain update not until early 2027. Read that timeline again: Operations interrupted in March may not be resolved until early next year. That's a year of impact for data and workloads that weren't migrated in time. Some of that data, I suspect, will never come back. I bring this up not to pile on AWS. Frankly, no cl ## AWS Cannot Restore Data Held Only in Damaged Middle East Availability Zones DevFeed: [AWS Cannot Restore Data Held Only in Damaged Middle East Availability Zones]() Original publisher: [Read original article]() Author: Steef-Jan Wiggers Published: 2026-09-21T08:43:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Amazon Web Services](), [Availability](), [data centers](), [data]() Tags: [architecture](), [architecture-design](), [availability](), [aws](), [aws-middle-east-data-loss](), [cloud](), [compliance](), [data](), [data-centers](), [development](), [devops](), [fault-tolerance](), [infrastructure](), [iran](), [news](), [reliability](), [uae]() ### AI overview AWS says it cannot restore resources and data hosted exclusively in a damaged Middle East availability zone in the UAE or exclusively in the Bahrain region. The report describes infrastructure damage that exceeded the resilience of regional and multi-Availability Zone services and discusses customer concerns about redundancy and data replication. ### Source excerpt AWS has told customers it cannot restore resources and data hosted exclusively in the mec1-az2 availability zone in the UAE, or exclusively in the Bahrain region, after damage during the conflict with Iran. The company says the Bahrain damage spanned multiple availability zones and exceeded what its regional and multi-AZ services are designed to withstand. By Steef-Jan Wiggers ## Getting started with Stripe in the UAE: A comprehensive guide for developers DevFeed: [Getting started with Stripe in the UAE: A comprehensive guide for developers]() Original publisher: [Read original article]() Author: Soad Abuelnaga Published: 2024-11-25T00:00:00Z Content type: tutorial Language: en Sources: [Stripe Dot Dev Blog]() Topics: [stripe](), [Product Management]() Tags: [e-commerce](), [for-developers](), [fraud](), [payment-processing](), [stripe](), [uae]() ### AI overview The article introduces Stripe's payment-processing features for developers in the UAE, including automated billing, fraud protection, and multi-currency support, for streamlining e-commerce operations. ### Source excerpt Stripe has emerged as a vital payment processing platform in the UAE, offering diverse features like automated billing, fraud protection, and multi-currency support, empowering developers to streamline e-commerce operations.