Transitioning from Tag Namespace and Keys
To enhance the security and efficiency of the JMS Fleets service, JMS Fleets is replacing the use of tag namespace and keys to register managed instances. Users who have set up JMS Fleets before August 7, 2024 are required to review and update their existing JMS Fleets service policies before July 1, 2025 23:59 UTC to ensure continued service functionality.
Action required
- Update your JMS Fleets policies to align with the new registration method:
- If you have set up JMS Fleets policies using the onboarding wizard, run the wizard again to update your policies.
- If you have manually configured JMS Fleets policies, add the policies listed in Summary of Changes.
- Update your Management Agent installation method:
- If you have been using an older installation script for Installing Management Agent and Deploying JMS Plug-in, you need to stop using the old script.
- Obtain the latest Oracle Management Agent installer or installation script by using the Download Agent Installer action from the JMS Fleet.
Summary of changes
Manage OCI resources required for JMS Fleets
Manage metrics
To manage metrics, the following policy statement has been added:
ALLOW DYNAMIC-GROUP JMS_DYNAMIC_GROUP TO MANAGE metrics IN COMPARTMENT Fleet_Compartment WHERE target.metrics.namespace='java_management_service'Manage JMS plugins
To manage JMS plugins, the following policy statements have been added:
ALLOW GROUP FLEET_MANAGERS TO MANAGE jms-plugins IN COMPARTMENT Fleet_Compartment
ALLOW dynamic-group JMS_DYNAMIC_GROUP TO MANAGE jms-plugins IN COMPARTMENT Fleet_CompartmentSee JMS Fleets Policy Statements for a list of policy statements used in JMS.