How to tackle configuration file in Jenkins?

There are some configurations in my code (to connect DB). I wrote them in .env. Users need to create their own .env file to run the application. This is the copy code in Dockerfile: COPY .env server COPY .env test

When I use Jenkins to build a pipline, I have to commit this file, but I should not do that(aws information included there).

What is the best practice to save configuration file?

Thanks