This configuration is fine, although I recommend also offering one of the ChaCha20-Poly1305 suites and making that suite the preferred option. I would suggest that you offer
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 if you are using RSA certificates, or
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 if you are using ECDSA certificates.
The reason for this is performance. AES-GCM uses some operations that are not fast without hardware acceleration. Specifically, the AES instruction set extension and carryless multiplication (e.g. PCLMULQDQ, XMULX) are used to perform the block cipher encryption and carryless multiplication over GF(2k) for GHASH respectively. Without these extensions the performance of AES-GCM is particularly poor. This primarily affects smartphones which may have AES extensions (only on ARMv8 architecutres) but will not provide the necessary carryless multiply extensions.
ChaCha20-Poly1305, however, relies only upon SIMD instructions for performance. These are fairly ubiquitous. All modern x86_64 processors and most high-end ARM processors offer a range of SIMD instruction extensions (e.g. SSE4, AVX2, NEON, etc.) which can enable highly efficient and performant implementations of ChaCha20-Poly1305.
Additionally, referencing back to my mention of ECDSA certificates, you may want to consider them instead of traditional RSA certificates. All modern browsers support such certificates and they, again, offer improved performance. ECDSA is also considered to be more future-proof against new attacks and is generally more straightforward from a security perspective (RSA has a lot of problems you have to mitigate when writing an implementation). If you do choose ECDSA certificates, you'll need to swap your existing configuration to use
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 for GCM.