If you’re running Amazon Aurora and want to take advantage of the Graviton3-based r7g instance types for better performance and efficiency, you might notice that sometimes the option doesn’t appear in the AWS console. Here’s a breakdown of why that happens and how to fix it.
Why You Might Not See r7g in the Console
When modifying an Aurora instance, only certain instance types are shown in the dropdown. If you’re missing r7g options, the most common reasons are:
- Aurora Engine Version
- r7g instances require Aurora MySQL 3.x+ (based on MySQL 8.0) or Aurora PostgreSQL 15+.
- Older versions, like Aurora MySQL 2.x, do not support r7g.
- Cluster Mode
- r7g is supported only in provisioned clusters.
- Aurora Serverless v1 and some global database setups do not allow Graviton3-based instances.
- Region Limitations
- Not every AWS region offers all instance classes.
- Make sure r7g is available in your region.
How to Check Your Aurora Version
To determine whether your Aurora cluster supports r7g:
- Open the RDS console.
- Navigate to Databases and click your Aurora cluster.
- Check the Aurora MySQL or Aurora PostgreSQL version under the instance details.
How to Upgrade to r7g
If your version and cluster type support r7g, here’s how to upgrade:
Using the AWS Management Console
- Open your Aurora instance in RDS.
- Click Modify.
- Under DB instance class, select the r7g instance type you want (e.g., db.r7g.2xlarge).
- Choose whether to apply immediately or during the next maintenance window.
- Click Continue, then Modify DB Instance.
⚠️ Note: Applying immediately will cause a brief downtime.
Using the AWS CLI
The console sometimes hides options. You can try the CLI for a more direct approach:
aws rds modify-db-instance \
–db-instance-identifier your-db-instance-id \
–db-instance-class db.r7g.2xlarge \
–apply-immediately
If your instance is not compatible, AWS will return an error specifying why (e.g., unsupported engine version).
Key Takeaways
- Only Aurora MySQL 3.x+ or Aurora PostgreSQL 15+ support r7g.
- Ensure your cluster is provisioned, not serverless.
- Check regional availability if the instance class is missing.
- Use the CLI if the console doesn’t show the instance type — it provides clearer error messages.
Upgrading to r7g can deliver better performance per dollar, thanks to AWS Graviton3 processors — but compatibility depends on your Aurora version, cluster mode, and region.
The Role of an ERP Implementation Partner
NewsEnterprise resource planning (ERP) implementations have evolved far beyond simple software deployments, becoming long-term business transformation initiatives that require strategic planning, change management, and ongoing support. In an article from ERP Today written by Garrett Rochell, he explains why choosing the right ERP partner can have a major impact on operational success, scalability, and long-term return on investment (ROI). The article emphasizes that an ERP implementation partner should act more like a business consultant than a software vendor. Their role begins before deployment through discovery, planning, and customization, then continues long after go-live with training, support, optimization, and scalability guidance. Rather than focusing solely on technical setup, strong partners take a holistic view of the organization and align ERP systems with broader business goals. One of the key themes is the importance of change management. ERP projects often struggle not because of the software itself, but because employees resist new processes or organizations fail to prepare teams for adoption. The article highlights how experienced implementation partners help reduce these risks through staff training, sandbox testing, proactive communication, and phased rollouts designed to minimize disruption. Rochell also stresses the value of industry expertise. ERP systems frequently require customization based on operational workflows, compliance needs, and reporting structures unique to a business’s sector. Partners with deep industry knowledge are better positioned to guide organizations through data migration, integration challenges, and long-term optimization strategies. Moreover, Rochell positions ERP implementation as an ongoing partnership rather than a one-time project. Businesses that choose partners focused on collaboration, continuous improvement, and strategic value creation are more likely to achieve lasting benefits from their ERP investment.
For Full Article, Click Here
How to Upgrade an AWS Aurora Instance to an r7g Instance Type
Articles, Frontpage Article, NewsIf you’re running Amazon Aurora and want to take advantage of the Graviton3-based r7g instance types for better performance and efficiency, you might notice that sometimes the option doesn’t appear in the AWS console. Here’s a breakdown of why that happens and how to fix it.
Why You Might Not See r7g in the Console
When modifying an Aurora instance, only certain instance types are shown in the dropdown. If you’re missing r7g options, the most common reasons are:
How to Check Your Aurora Version
To determine whether your Aurora cluster supports r7g:
How to Upgrade to r7g
If your version and cluster type support r7g, here’s how to upgrade:
Using the AWS Management Console
⚠️ Note: Applying immediately will cause a brief downtime.
Using the AWS CLI
The console sometimes hides options. You can try the CLI for a more direct approach:
aws rds modify-db-instance \
–db-instance-identifier your-db-instance-id \
–db-instance-class db.r7g.2xlarge \
–apply-immediately
If your instance is not compatible, AWS will return an error specifying why (e.g., unsupported engine version).
Key Takeaways
Upgrading to r7g can deliver better performance per dollar, thanks to AWS Graviton3 processors — but compatibility depends on your Aurora version, cluster mode, and region.
Why Late Change Management Dooms ERP Transformation Projects
NewsEnterprise Resource Planning (ERP) transformation projects often focus heavily on technology, but many fail because organizations underestimate the human side of change. In a recent article from ERP Today by contributor Jessica Browne, it explains how delaying change management efforts can create resistance, slow adoption, and ultimately undermine the success of large-scale ERP initiatives. Browne argues that change management should begin at the very start of an ERP project—not near deployment or after major decisions have already been made. When employees are brought into the process too late, confusion and skepticism can grow quickly. Teams may struggle to understand why changes are happening, how workflows will evolve, or what the long-term benefits will be for the organization and their day-to-day responsibilities. Another key point is that ERP transformations impact far more than software systems. They often require organizations to rethink processes, responsibilities, reporting structures, and internal collaboration. Without early communication and leadership alignment, businesses risk creating friction between departments and slowing overall adoption. The article highlights the importance of building trust through transparency, ongoing training, and active employee engagement throughout the project lifecycle.
The article also emphasizes that successful ERP implementations depend on executive sponsorship and consistent messaging from leadership. Employees are more likely to embrace transformation efforts when leaders clearly communicate goals, expected outcomes, and how the changes support broader business objectives. Change management is presented not as a secondary task, but as a core strategic function that directly influences project success.
ERP transformation is as much about people as it is about technology. Organizations that prioritize change management early are far more likely to achieve smoother adoption, stronger user engagement, and better long-term outcomes from their ERP investments.
For Full Article, Click Here
Organizations Must Confront the AI-ERP Reality Gap
NewsArtificial Intelligence (AI) is generating enormous excitement across the enterprise, but many organizations are discovering that their enterprise resource planning (ERP) foundations are not ready to support their AI ambitions. An article from ERP Today by Gertjan van der Linden argues that the biggest barrier to AI success is often not the technology itself, but the outdated ERP environments underneath it. The article explains that many companies are racing to deploy AI-driven analytics, automation, and decision-support tools without addressing years of ERP customization, technical debt, and fragmented data. While these AI initiatives can produce promising pilot projects, they often struggle to scale because the underlying systems lack the process consistency, governance, and data quality AI requires to operate effectively. A key theme is that ERP and AI should not be treated as separate initiatives. Modern ERP systems are evolving from systems of record into systems of orchestration, providing the trusted data, standardized processes, and governance frameworks that allow AI to deliver sustainable business value. Organizations that view ERP modernization and AI adoption as a single transformation effort are more likely to achieve meaningful results. The article also highlights the importance of reducing unnecessary customization, strengthening data governance, and investing in employee training so teams can effectively work alongside AI-powered tools. Perhaps most importantly, organizations should design ERP processes with AI in mind during implementation rather than attempting costly retrofits later. Ultimately, AI success depends on ERP readiness. Companies that strengthen their ERP core, improve data quality, and build AI-aware processes today will be better positioned to turn AI investments into long-term operational and competitive advantages.
For Full Article, Click Here
Weekly Patch Notification: June 20, 2026
Articles, Frontpage Article, PatchesRunning the Pre-Sync Data Check for Actor Data
Articles, Frontpage Article, NewsIf you are getting errors when provisioning users, these errors cannot be auto-corrected.
In SSOCONFIG, use the Data Check for Actor data which identifies errors that exist so you can fix them manually.
From the LSF server, run the ssoconfig utility.
ssoconfig -c- enter the ssoconfig utility password when prompted.
Results of the Pre-Sync Data Check are written to the security log file LAWDIR/system/security_provisioning.log
Upcoming Events July 2026
EventsThe Carolinas User Exchange is hosting a Free speaker event with Infor this July! Check out the details below and mark your calendars. Additional events will be added throughout the month so be sure to come back and check for more Infor-related events.
You’re Invited: Free Speaker Event with Infor!
Hosted by: Carolinas User Exchange
When: Thursday, July 9th, 2026 from 2:30 to 4:00 (US/Eastern)
Join us for an engaging and insightful session led by Jana Rogers from Infor, focusing on “CU Process Lessons Learned”. This free speaker event is a great opportunity to learn from an industry expert bringing deep knowledge and practical experience to the conversation.
Session Overview:
Preparing for releases and the CU process: A Customer Perspective. This presentation will dive into practical strategies for planning, absorbing, and operationalizing the CU cadence, with a strong focus on how to adopt new features without disrupting daily operations. The session will cover balancing release adoption, testing cycles, and operational readiness while still delivering value from new functionality. Attendees can expect to learn about release impact assessment, cross-functional coordination, testing prioritization, and change communication, all designed to help teams shift from reactive updates to a more predictable, disciplined, and value-driven CU process.
Reserve your spot today and take advantage of this valuable learning opportunity. We look forward to seeing you there!
Event-Driven Agentic AI: What Happens When ERP Becomes the Operator
NewsEnterprise resource planning (ERP) systems are evolving beyond static transaction engines into intelligent, responsive platforms that can act in real time. In a recent article from ERP Today the author – Robert Kramer of KramerERP – explores how event-driven architecture and agentic AI are reshaping ERP into an active operator within the enterprise. A core idea in the article is the shift from traditional, user-driven ERP systems to event-driven systems that respond automatically to business triggers. Instead of waiting for manual input or scheduled batch processes, ERP systems can now react instantly to events such as inventory changes, supply chain disruptions, or production issues. Layered on top of this is the rise of agentic AI, where autonomous digital agents can execute workflows, coordinate actions across systems, and make decisions within defined governance rules. These agents reduce manual effort by handling tasks like procurement, scheduling, reconciliation, and exception management—while escalating edge cases to humans when needed. Kramer emphasizes that this evolution transforms ERP from a passive system of record into a proactive “operator” that orchestrates business processes in real time. The article also highlights the growing importance of cross-system agent collaboration, where ERP agents interact with CRM, SCM, and other enterprise systems to coordinate end-to-end workflows. However, the shift also introduces challenges around governance, data quality, integration complexity, and workforce adaptation. Organizations must define clear boundaries for autonomy and ensure strong oversight of agent-driven actions. Ultimately, Kramer positions event-driven agentic ERP as a major step toward more responsive, automated, and intelligent enterprise operations—where systems don’t just record work, but actively drive it.
For Full Article, Click Here
Autonomous Enterprise versus Composable ERP
NewsAs ERP (enterprise resource planning) systems continue to evolve, businesses are increasingly balancing the promise of autonomous operations with the flexibility of composable ERP environments. In an article from E3 Magazine, Editor-in-Chief Peter M. Färbinger examines how organizations are rethinking ERP strategies to better support automation, agility, and long-term digital transformation. The article explains that the “autonomous enterprise” concept focuses on AI-driven systems capable of analyzing data, automating workflows, and making operational decisions with minimal human involvement. The goal is to improve efficiency, reduce repetitive manual tasks, and help businesses respond more quickly to changing demands. At the same time, composable ERP emphasizes flexibility through modular applications and services that can be integrated based on a company’s specific needs. Rather than relying on one rigid platform, organizations can build adaptable ecosystems that evolve alongside the business. This approach allows companies to adopt new technologies faster and avoid the limitations of traditional monolithic ERP systems. A major takeaway from the article is that these strategies are not mutually exclusive. In fact, composable ERP may provide the ideal foundation for autonomous capabilities by making it easier to integrate AI tools, automate processes, and scale innovation across departments. Ultimately, Färbinger suggests that businesses combining flexibility with intelligent automation will be best positioned for the future of ERP and enterprise transformation.
For Full Article, Click Here
Lawson Error – “Unable to log on RUNUSERKEY Account”
Articles, Frontpage Article, NewsIf you run into this error, it likely means that many of your batch jobs in Lawson are going into recovery. The reason this may have occurred is due to a domain name change or possibly an accidental password reset.
To resolve, first login into LSA, then go to Manage Privileged Identities.
Once there, click the Environment named service ie. LSFPROD, LSFTEST or however yours is named. Select the BATCH key and find out what user is assigned under it.
This BATCH key may be named differently so check your lajs.cfg file under RUNUSERKEY as shown below in the system folder.

If you know the latest password login to LID with it first to confirm.
After confirming, type the password in the password field shown below and remember to click CHANGE after you confirm the password:
If you’re able to track down the right user and update the password, your jobs should recover without too much trouble. If errors like this keep popping up or if you would rather not spend time digging through configs and logs, our managed services team can step in. With a dedicated group of Lawson experts behind you, we handle issues like batch job failures, user access, and system troubleshooting so your team doesn’t have to. Our goal is to keep your Lawson environment stable and reliable while you focus on running the business.