<p><a href="https://aws.amazon.com/iam/roles-anywhere/">AWS Identity and Access Management (IAM) Roles Anywhere</a> now provides a plugin for the <a href="https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/home.html">AWS SDK for Java v2</a> that enables workloads running outside of AWS to obtain temporary AWS credentials directly within the Java application process. The plugin runs in the same Java Virtual Machine (JVM) as your application, removing the need to run the IAM Roles Anywhere credential helper as a separate process or configure credential_process in your AWS profile.<br> <br> You configure the plugin on your AWS SDK for Java v2 service client builder to automatically resolve temporary credentials without writing credential-fetching logic. The plugin handles calling CreateSession and automatically refreshing credentials before they expire. It supports RSA, Elliptic Curve (EC), and ML-DSA key types and requires Java 8 or higher. There is no additional charge for using the plugin.<br> <br> IAM Roles Anywhere is available in all <a href="https://docs.aws.amazon.com/general/latest/gr/rolesanywhere.html">AWS Regions</a>, including the AWS GovCloud (US) Regions, AWS European Sovereign Cloud (Germany) Region, and China Regions. To get started with the Java plugin, see the <a href="https://docs.aws.amazon.com/rolesanywhere/latest/userguide/java-plugin.html">IAM Roles Anywhere Java plugin documentation</a>. For the current version, release notes, and signature verification instructions, see the <a href="https://central.sonatype.com/artifact/software.amazon.rolesanywhere.plugin/roles-anywhere-java">plugin's page</a> on the Maven Central website and the <a href="https://github.com/aws-sdk-plugin/roles-anywhere-java">roles-anywhere-java repository</a> on GitHub.</p>
IAM Roles Anywhere now provides a Java plugin for the AWS SDK
AWS Identity and Access Management (IAM) Roles Anywhere now provides a plugin for the AWS SDK for Java v2 that enables workloads running outside of AWS to obtain temporary AWS credentials directly within the Java application process. The plugin runs in the same Java Virtual Machi

Pexels (free commercial use)
Related stories

Anthropic pushes into physical world with new standard to help AI agents operate machines - CNBC
Anthropic News
Anthropic pushes into physical world with new standard to help AI agents operate machines CNBC
AWS Elastic Disaster Recovery introduces Recovery Plans for orchestrated application recovery
AWS What’s New
AWS Elastic Disaster Recovery (AWS DRS) now offers Recovery Plans, a capability that automates the sequential launch of multi-server applications during recovery and drills. Instead of launching servers one at a time and tracking dependencies manually, you define the recovery seq

Giga-Scale AI and the Ethernet Evolution: How Spectrum-X Ethernet Rewrites the Rules
NVIDIA Developer Blog
The massive growth of generative AI has fundamentally altered data center design. As distributed model training scales to span hundreds of thousands of GPUs,... The massive growth of generative AI has fundamentally altered data center design. As distributed model training scales

How AI Coding Agents Can Unlock Materials Simulation with NVIDIA ALCHEMI Toolkit
NVIDIA Developer Blog
Atomistic simulation requires three things: knowledge of the science, compute-efficient implementation of simulations, and accessible interfaces to the... Atomistic simulation requires three things: knowledge of the science, compute-efficient implementation of simulations, and ac

How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache
Sebastiaan Neuteboom
Big Pineapple , the platform behind 1.1.1.1 , Gateway DNS , DNS Firewall , AS112 , and several other Cloudflare DNS services, stores over 250 billion DNS cache entries at any given time. At that scale, wasting a single byte per entry costs more than 250 gigabytes of memory across

Managed PostgreSQL vs. self-hosted PostgreSQL: Key benefits and trade-offs
Lauro Ojeda
Summary This post is for technical decision makers evaluating where to run production PostgreSQL workloads. It compares two valid operating models—self-managed PostgreSQL and a managed database service—through business and operational outcomes: control, engineering capacity, resi
