CloudFormation - LaunchTemplate for Elastic Beanstalk Environment

We are using aws:autoscaling:launchconfiguration namespace to configure things like InstanceType, SSHSourceRestriction, etc.

When creating a NEW eb environment, A Launch configuration is still getting created. Once we add DisableIMDSv1 option to the cloudformation, a launch template is created instead of launch configuration.

Questions:

1. Can we continue to use "aws:autoscaling:launchconfiguration" namespace to configure things like InstanceType, SSHSourceRestriction ?
2. Will there be a namespace like "aws:autoscaling:launchtemplate" in the future?

A year later I'm still seeing the same thing as @Max-85: If you create a new stack based on the latest elastic beanstalk example template, you'll still get an AWS::AutoScaling::LaunchConfiguration instead of a launch template.

The docs for aws:autoscaling:launchconfiguration say:

The instances that are used for your environment are created using either an Amazon EC2 launch template or an Auto Scaling group launch configuration resource. The following options work with both of these resource types.

And it turns out you can use these options to configure a launch template, but you'll need to disable IMDSv1 expliticly in your cloudformation template, as follows (in the OptionSettings for the AWS::ElasticBeanstalk::ConfigurationTemplate):

Properties:
  ...
  - Namespace: aws:autoscaling:launchconfiguration
    OptionName: DisableIMDSv1
    Value: true