[devanshraghuvanshi]

Logging Service:

• Added loggingS3Destination.region: "us-east-1" support to example-config/.../ibm-mas-masapp-configs.yaml.
• Secret creation template 01-ibm-manage_logging_secrets.yaml handles secret creation conditionally (accessSecretKey).

Customization Archive (S3):

• Added customizationArchive.useS3.region schema to values.yaml and README.md.
• Enhanced 01-ibm-manage_customization_archive_secrets.yaml to support S3 secret tokens (accessSecretKey / secretKey) when access_secret_key is supplied, while maintaining full backward compatibility with username/password basic auth.

Global Fallback:

• Added defaultRegion: "us-east-1" to example configs and documentation.

Backward Compatibility:

• All secrets are created only if their respective configurations exist, leaving legacy bundleLevelProperties configurations unaffected.

[devanshraghuvanshi]

Testing result:

[devanshraghuvanshi]

End-to-End Fresh Instance Provisioning Test Summary — noble8 / inst01

GitOps Branch: test-MAXMF-8126
Environment: noble8
Instance: inst01

1. Prerequisites and Instance Provisioning

• Mongo, SLS, Db2 (db2u-inst01), and MAS Suite core were deployed and reached Ready.
• ManageApp reached Ready on version 9.2.5-pre.maint92xdev.
• Maximo database initialization (maxinst) and image builds completed successfully.
• ManageWorkspace inst01-main rendered with defaultRegion: us-east-2 and loggingS3Destination.region: us-east-2.
• Server bundle pods (inst01-main-default-*, 2/2 replicas) and JMS server (inst01-main-jmsserver-0, 1/1 replica) reached Running.
• Internal health probe /maximo/api/ping?ready=1 returned {"mxserverstarted": true}.

2. S3 Logging Destination and Region Handling

• Created S3 bucket mas-logging-inst01-noble8 in us-east-2.
• Updated AWS Secrets Manager path fyre-noble8-dev/noble8/inst01/manage_logging/cos-logging.
• Verified dynamic population of Kubernetes secret cos-logging in namespace mas-inst01-manage.
• Successfully uploaded, listed, and downloaded a test log payload at s3://mas-logging-inst01-noble8/manage-logs/inst01-test-log.zip.
• Verified the downloaded payload matched the expected test content.

Result: S3 logging read/write verification passed.

3. Customization Archive S3 Build Verification

• Uploaded manage-lafix.zip to s3://mas-logging-inst01-noble8/customizations/manage-lafix.zip in us-east-2.
• Created secret custom-s3-credentials in mas-inst01-manage using the dual-key schema (accessSecretKey and secretKey).
• Successfully downloaded the archive from S3 and extracted it.
• Verified the extracted README.txt contained the expected test customization content.

Result: Customization archive S3 download and extraction simulation passed.

4. Backward Compatibility

• Verified existing instance inst03 on noble8, with region fields omitted, continued running normally in Ready state without failures.

Overall Result: Fresh instance provisioning, Manage health checks, S3 region routing, logging read/write, customization archive download/extraction, and backward compatibility checks passed.