LogConfig in core.yaml is not working as expected when set to awslogs

I am trying to set the logging driver for all containers(including chaincode containers) in Hyperledger Fabric v2.2.0.

I know that there is no way to manage chaincode containers in fabric and they are being created at the time of instantiation of chaincode. But in core.yaml file, there is a vm section, which configures the docker containers. I tried changing the LogConfig section to push container logs to aws cloudwatch. Here is the vm section in core.yaml which I changed –

 ###############################################################################
#
#    VM section
#
###############################################################################
vm:

    # Endpoint of the vm management system.  For docker can be one of the following in general
    # unix:///var/run/docker.sock
    # http://localhost:2375
    # https://localhost:2376
    endpoint: unix:///var/run/docker.sock

    # settings for docker vms
    docker:
        tls:
            enabled: false
            ca:
                file: docker/ca.crt
            cert:
                file: docker/tls.crt
            key:
                file: docker/tls.key

        # Enables/disables the standard out/err from chaincode containers for
        # debugging purposes
        attachStdout: false

        # Parameters on creating docker container.
        # Container may be efficiently created using ipam & dns-server for cluster
        # NetworkMode - sets the networking mode for the container. Supported
        # standard values are: `host`(default),`bridge`,`ipvlan`,`none`.
        # Dns - a list of DNS servers for the container to use.
        # Note:  `Privileged` `Binds` `Links` and `PortBindings` properties of
        # Docker Host Config are not supported and will not be used if set.
        # LogConfig - sets the logging driver (Type) and related options
        # (Config) for Docker. For more info,
        # https://docs.docker.com/engine/admin/logging/overview/
        # Note: Set LogConfig using Environment Variables is not supported.
        hostConfig:
            NetworkMode: host
            Dns:
               # - 192.168.0.1
            LogConfig:
                Type: awslogs #json-file
                Config:
                    awslogs-region: eu-west-1
                    awslogs-group: docker-logs
                    #awslogs-stream: 
                    # max-size: "50m"
                    # max-file: "5"
            Memory: 2147483648

After changing the configuration, I started the network and created the containers and then checked that the log configuration has been applied or not

$ docker inspect -f '{{.HostConfig.LogConfig.Type}}' servicename
json-file

Expected to see: awslogs, but saw json-file.

The log entries should have been sent to the Cloudwatch but the Cloudwatch log group is empty.

Here is the core.yaml which I used in my network –
https://github.com/hyperledger/fabric/blob/master/sampleconfig/core.yaml

Source: Docker Questions