Solution 1:

AWS CDK's main purpose is to provision infrastructure. Managing the data stored on those infrastructure is an entirely different story.

Deploying Updates to Static Site
If the goal of this rename operation is for deployment purposes, I would suggest to just use AWS CLI, this makes release process much simpler with less risk as the underlying infrastructure is not at risk of unintentional modifications / bugs in the updates made on the infrastructure's CDK templates.

This option makes mounting on a CI/CD pipeline much more simpler too!

Managing application data If the goal of this rename is to manage application data, I would suggest using AWS SDK for your language of choice.

Layering automation is a subtle best practice! Using these automation tools for the right goal / use-cases can empower us to deliver changes quicker to customers!