# Datomic Cloud 1102-9309
**URL:** https://forum.datomic.com/t/datomic-cloud-1102-9309/2347
**Category:** Announcements
**Created:** [December 20, 2023, 9:56pm UTC](https://forum.datomic.com/t/datomic-cloud-1102-9309/2347 "2023-12-20T21:56:31Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@jaret](https://forum.datomic.com/u/jaret)
#### Post date: [December 20, 2023, 9:56pm UTC](https://forum.datomic.com/t/datomic-cloud-1102-9309/2347/1 "2023-12-20T21:56:31Z")
This message covers changes in this release.
- [critical release notices](https://docs.datomic.com/cloud/releases.html#critical-notices)
- [all release notes](https://docs.datomic.com/cloud/changes.html)
## 2023/12/20 1102-9309
- Enhancement: Migrate CloudFormation templates to use AutoScalingGroup LaunchTemplate instead of the deprecated LaunchConfiguration.
- Fix: Pull expression could return true when supplying a :default for a boolean attribute.
- Fix: Regression introduced in 990-9202 that could cause a database with blank keyword idents to fail to load.
- Performance: Replace BufferedInputStream with an unsynchronized stream.
- Upgrade CFT Lambda Runtime to nodejs18.x
- Upgraded core.async to 1.6.681
- Upgraded commons-codec to 1.16.0
- Upgraded aws-java-sdk-bundle to 1.12.564
- Upgraded memcache-asg-java-client to 1.1.0.36
- Upgraded http-client to 1.0.126
- Upgraded transit-clj to 1.0.333
- Upgraded client-cloud to 1.0.124
- Upgraded fressian to 0.6.8
- Upgraded guava to 32.0.1-jre
- Upgraded jul-to-slf4j to 1.7.36
- Upgraded log4j-over-slf4j to 1.7.36
- Upgraded jcl-over-slf4j to 1.7.36
- Upgraded tools.namespace to 1.4.4
- Upgrade The AMI is now based on the [2023/10/16](https://docs.aws.amazon.com/linux/al2023/release-notes/relnotes-2023.2.20231016.html) version of the Linux 2023 base AMI.
Templates here:
> **[Datomic Change Logs | Datomic](https://docs.datomic.com/changes.html)**
---
### Author:  [@onetom](https://forum.datomic.com/u/onetom)
#### Post date: [December 22, 2023, 2:55am UTC](https://forum.datomic.com/t/datomic-cloud-1102-9309/2347/2 "2023-12-22T02:55:33Z")
Can we or should we upgrade the `com.datomic/{ion,client-cloud,local,ion-dev}` libraries before upgrading the stacks or the other way around?
I tried to look for an answer here, but haven’t noticed any:
[https://docs.datomic.com/cloud/operation/upgrading.html#compute-only-upgrade](https://docs.datomic.com/cloud/operation/upgrading.html#compute-only-upgrade)
---
### Author:  [@daemianmack](https://forum.datomic.com/u/daemianmack)
#### Post date: [December 25, 2023, 1:20am UTC](https://forum.datomic.com/t/datomic-cloud-1102-9309/2347/3 "2023-12-25T01:20:20Z")
> Regression introduced in 990-9202 that could cause a database with blank keyword idents to fail to load.
Can you expand on what is meant by “with blank keyword idents”?
---
### Author:  [@onetom](https://forum.datomic.com/u/onetom)
#### Post date: [December 27, 2023, 6:12am UTC](https://forum.datomic.com/t/datomic-cloud-1102-9309/2347/4 "2023-12-27T06:12:22Z")
My guess would be entities like this: `{:db/ident (keyword "\n \t\r")}`
---
### Author:  [@jaret](https://forum.datomic.com/u/jaret)
#### Post date: [December 27, 2023, 12:39pm UTC](https://forum.datomic.com/t/datomic-cloud-1102-9309/2347/5 "2023-12-27T12:39:23Z")
@daemianmack and @onetom,
Previous versions of Datomic Cloud would allow you to transact stuff like this:
```auto
(d/transact conn {:tx-data [[:db/add "123457" :db/ident (keyword "")]]})
```
We had a few folks who had idents like this on their system from ETL work and when we made another change in 990 to how DBs were loaded we discovered that users had keywords like `:` on their system and that caused an error and caught these “blank” idents.
---
### Author:  [@daemianmack](https://forum.datomic.com/u/daemianmack)
#### Post date: [December 27, 2023, 1:10pm UTC](https://forum.datomic.com/t/datomic-cloud-1102-9309/2347/6 "2023-12-27T13:10:03Z")
Got it, thanks!