Additional VB for AWS instance?

[abelliniSIBA]

Hello,

do you think it could be possible to have a second appliance connected through the plugin to VBR Console?

As we are planning to move several services from a single account architecture to a multi one.
This could be helpful to protect our actual environment (keeping existing backups) while building a newer structure in parallel.

Thanks in advance for your advice

Best Regards

Alessandro Bellini

[nielsengelen]

Hi,

VB for AWS does support multiple accounts via IAM roles. Did you already look into this? Or could you clarify the reason/choice for multiple appliances?

[abelliniSIBA]

Hello Nielsen,

thanks for your quick reply,
the reason is to keep the actual production instance working "as is" for entire duration of the migration process
from a single-account A (one appliance using S3 bucket, snapshot policy and IAM role only for account A)
to a multi-account architecture (new one with different S3 bucket, snapshots and IAM role for account B,C,D,E,F)
Moving protected instances from one env to the other while keeping the backup chain history in case of need
and VBR as central repo for VUL License distribution and reporting.
At the end closing the single-account appliance.
This could be also easier to keep separated roles and policies from single to multi account references.

I'm just thinking about the best way to achieve this,
Thanks again for your help

Regards
Alessandro Bellini

[nielsengelen]

Understood, so you just want a "fresh" start. It is possible to add multiple instances to VBR without any issues. A VB for AWS instance can only be linked to 1 VBR installation though.

I think your process is ok to use a fresh setup for the multi-account configuration and clarification per roles/policies/...

[abelliniSIBA]

Thanks Nielsen!

I will follow this process, thanks for your clarification.
Regards

Alessandro Bellini