I’m currently having an issue where the file imports defined on the .ebextensions folder don’t end up on their target paths. My current configuration (located on .ebextensions/credentials.config) is the following:

files:     "/var/app/current/credentials.json":         mode: "000644"         owner: root         group: root         source: "https://bucket-name.s3.region.amazonaws.com/credentials.json"         authentication: S3Access  Resources:     AWSEBAutoScalingGroup:         Metadata:             AWS::CloudFormation::Authentication:                 S3Access:                     type: S3                     roleName: aws-elasticbeanstalk-ec2-role                     buckets: bucket-name 

• There is not a single error indicating this file import isn’t working
• the specified file only appears on /var/app/current/credentials.json whenever there is a configuration change on this config file
• when the env is updated without changing this config file, the specified file is not present on the ec2 instances.

The only reason I can think about why this would happen is that beanstalk is replacing the contents of /var/app/current/, after importing the file, thus deleting it.