IME, the perception that option 1 means no maintenance is a false hope. AWS (or any cloud provider) will also update it's API, there will always be new offerings. There will always be changes.
So I definitely agree the goal is to pave/gold paint the sensible defaults and then expose override options.
To extend further though, IMO you should either give the devs AWS, or build a platform, but not create just an in house pass through to AWS. IME when you create a pass through when things go wrong, there is a hard to debate battle of if it's AWS or your platform. The platform team ends up saying "but it's just AWS!" and the app team says "but I'm asking via your platform!". Both are right but neither is helpful 😅
If you go platform, IMO your interface should be customer (app team) informed and usable, and your features/offerings should include the codification of any business requirements.