need a way to change Lightsail Bitnami+Wordpress to ipv6 only

Question

I've been trying to get this working for half a day now.

Obviously I can't create a new instance from my snapshot because that blueprint doesn't support ipv6 only. So it was recommended I create a new disk  snapshot from command line, except that gives me error 
> lightsail:CreateDiskSnapshot on resource: arn:aws:lightsail:ap-northeast-1:XXXXXXXX:* because no identity-based policy allows the lightsail:CreateDiskSnapshot action

OK, so someone told me I need to use something called IAM, and after much fighting with it, I was able to create a new user and add the right permissions for CreateDiskSnapshot, except that user can't see my instance. And I can't work out how to use IAM to add the necessary permissions for the existing user that created the instance

All I want is to switch my instance to to ipv6 only. I don't even use wordpress and don't care if it stops working. Surely there has to be some easy way to do this

Thanks in advance for all advice

AWS-SUM · Answer

Hi,

Sorry to hear about your troubles.

If you do not need WordPress, you could launch an instance of the OS-only blueprints such as Debian (to match the OS of the WordPress instance) and then attach a disk created from the root disk snapshot of your current instance to this new instance and copy over data from the disk.

Once done with moving your data over and confident of your new setup you could delete the older instance, and detach and delete the attached disk as well. I would recommend taking instance-snapshots of both your old and new instances before deleting any resources.

Unfortunately there's no other way to `manually disabling ipv4` from your current WordPress instance. You will need to copy your application over and redo some setup.

To resolve the permission issue with creating the root disk snapshot, you have a few options ->

1. While logged into Lightsail console create the root-disk snapshot using CloudShell (browser-based AWS command line) that can be accessed from the console. Please refer [this doc](https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-cloudshell.html#lightsail-cloudshell-launch-and-use). If the user you are logged into the console with, has the required permissions the above will work.
2. Alternatively, one simple way to allow the IAM user that you have setup to use the command line to have all Lightsail permissions is to replace `lightsail:CreateDiskSnapshot` to `lightsail:*` in the IAM policy (the `*` means it has any and all Lightsail actions permitted). If you would like to edit IAM policy via the console please refer [this doc](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_manage-edit.html#edit-managed-policy-console)

Thanks.

yonda · Answer

yeah, I know all that. The workaround was what I was referencing in my original post. Sadly even if I could get it to work, its not a solution. I don't want to copy files, I need everything set up the way it is on my current instance. It took a week getting mercurial and everything set up to work, and I do not want to go through that again.

What if I don't care about wordpress? I'm fine if it stops working. Does that give me any more options?

> modifying existing instance: Editing configurations on your existing instance to disable IPv4 might lead to unexpected behavior and potential downtime. NOT RECOMMENDED

Interesting. Remember the whole point of this is to not have to pay the ridiculous new ipv4 fee. I'm not sure that me manually disabling ipv4 would stop Amazon from charging me the ipv4 fee. Or am I wrong?

Ganesh Kudikala · Answer

Hi

The Bitnami+WordPress blueprint in Lightsail doesn't currently support launching instances with IPv6-only networking. Refer https://repost.aws/questions/QU-GxT4XHlRjaKmpDWqjVbug/will-the-lightsail-bitnami-wordpress-blueprint-support-ipv6-only

Workaround  alternative approaches you can consider: https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-ipv6-only-plans.html#migrate-to-ipv6-only-plan

**Modifying existing instance**: Editing configurations on your existing instance to disable IPv4 might lead to unexpected behavior and potential downtime. NOT RECOMMENDED

need a way to change Lightsail Bitnami+Wordpress to ipv6 only

Relevant content