Currently cloudwatch logstream log uses s3_bucket/s3_bucket_path/datestamp/file as s3 location.
Because the s3_bucket and s3_bucket_path values are configured at stack manager layer, that means the mapping of this config is one per stack manager, which translates to multiple AEM environments to be sharing the same stack manager configuration.
In order to avoid the possibility of conflicting s3 location across multiple aem environments, we should introduce stack prefix to the s3 location to become s3_bucket/s3_bucket_path/stack_prefix/datestamp/file .
Orchestrator as the trigger of the scheduling, should ideally inject the stack_prefix value.
Currently cloudwatch logstream log uses s3_bucket/s3_bucket_path/datestamp/file as s3 location.
Because the s3_bucket and s3_bucket_path values are configured at stack manager layer, that means the mapping of this config is one per stack manager, which translates to multiple AEM environments to be sharing the same stack manager configuration.
In order to avoid the possibility of conflicting s3 location across multiple aem environments, we should introduce stack prefix to the s3 location to become s3_bucket/s3_bucket_path/stack_prefix/datestamp/file . Orchestrator as the trigger of the scheduling, should ideally inject the stack_prefix value.