AWS

The Register argues that AWS should pivot from trying to be a direct-to-consumer AI platform to acting as a robust wholesaler of underlying infrastructure. This shift acknowledges that enterprise buyers prefer to assemble their own AI stacks using modular components rather than relying on a monolithic vendor solution. The piece suggests this strategy aligns better with current market dynamics and customer preferences for flexibility.

• AWS is advised to stop competing as a direct AI platform provider for end users.
• Focus should shift to providing reliable, scalable wholesale infrastructure components.
• Enterprise customers generally prefer to build custom AI stacks from modular parts.
• This strategy reduces friction for buyers who value control and interoperability.
• The article frames this as a pragmatic business evolution rather than a failure.

AWS has enabled foreign key constraints in Aurora DSQL, allowing applications to enforce referential integrity directly within the database engine. This update includes support for standard actions like CASCADE and SET NULL, addressing a previously reported adoption barrier for users requiring strict data consistency. The feature closes a significant gap in the distributed SQL offering by moving integrity checks from the application layer to the database layer.

• Aurora DSQL now supports native foreign keys, reducing reliance on application-side validation logic.
• Referential actions like CASCADE and SET NULL are available for maintaining data consistency.
• This change removes a key adoption blocker for enterprises requiring strict database constraints.
• Developers can simplify data models by trusting the database engine for integrity checks.