SKU Groups - AlloyDB Compute

This page lists SKU Groups that may be referenced in contracts and Cost Management. SKU Groups may include Other Eligible Services for Google Cloud Enterprise Agreement customers. For more information, contact sales.

AlloyDB Compute

Service NameSKU NameSKU IDDate Added
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in BelgiumD80A-F203-F8F4March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Berlin9814-46F7-9A7AJanuary 23, 2024
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Columbus1B04-9189-C908March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Dallas8409-73E9-1E05March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Delhi5872-C07B-9968March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Finland872D-10E4-50EDMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in FrankfurtBFED-D9D0-B3A1March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Hong kong3588-62F4-3EFCMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in IowaF8AA-184E-4DBCMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in IsraelDF78-95B9-74DDMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in JakartaC9E2-8ED7-55E7March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in LA25B1-653B-8490March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Las Vegas06E1-7383-D619March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in London8317-9E3B-9FA7March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in MadridFA60-AE9A-1A51March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Melbourne8016-4D69-C5F2March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Milan3823-1103-805FMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in MontrealCA07-F1E4-BC55March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Mumbai6E09-F3D0-0DD2March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Netherlands979A-BA0D-91E7March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Northern Virginia233F-15CC-157EMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in OregonF853-370B-CE37March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in OsakaFA50-B152-4248March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Paris41AC-AC40-1902March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Salt Lake City45DC-A41D-649BMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Santiago2B5C-7CDA-63C1March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Seoul03D6-89BB-9E10March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in SingaporeABDE-FCCE-8FB8March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in South Carolina194B-D163-A311March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in SydneyE386-BEC7-7051March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in São Paulo0119-2C46-4942March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Taiwan9CF3-43BF-4950March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Tokyo8E97-EE92-F33CMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Toronto6E30-FE80-576CMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Warsaw8A6F-CB07-119CMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance RAM Usage in Zurich89E7-8092-4900March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in BelgiumFD6C-9739-1642March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in BerlinEBF3-4D84-D181January 23, 2024
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Columbus2F8B-E33A-5BBBMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in DallasBC52-8756-796CMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Delhi75A7-BB48-8FC2March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in FinlandF33D-5953-0EF5March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Frankfurt587A-E9EB-9E84March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Hong kongF4F5-1A69-69BBMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Iowa6F5E-021F-DC56March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Israel7EAC-7EB5-6972March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in JakartaFD85-5918-F06BMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in LAEAE9-E91F-7989March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Las VegasD5E5-E37D-F156March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in London1634-F851-9A05March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in MadridE539-ED60-8D5BMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in MelbourneFFEF-A8AE-D3ACMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Milan1A94-FE64-4969March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Montreal08E4-5FF6-DEE7March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Mumbai9155-5E0F-9E0CMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Netherlands3AB8-0CBF-1693March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Northern Virginia718D-9B7C-8026March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in OregonA7CB-AAC7-CA7BMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Osaka9011-41DB-B818March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Paris4320-4006-4485March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Salt Lake City28CB-2DEF-BBE9March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in SantiagoBE67-5B39-23D1March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Seoul6D5A-5C53-DFACMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Singapore8840-2760-29BBMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in South Carolina89BE-F9FC-C8CAMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Sydney6CF3-E050-D054March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in São Paulo1CA5-8A37-D73CMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Taiwan9FC5-A6A6-CF5BMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Tokyo8B0B-80D4-DACEMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Toronto750B-319D-992AMarch 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in WarsawF23B-5192-9B23March 4, 2023
AlloyDB
(C49F-B7F2-7416)
AlloyDB Instance vCPU Cores in Zurich734B-3BF0-AB57March 4, 2023