Hi Hartmut,
we do need an appliance to convert from the “normal” S3 objects to the bigger archive objects. This appliance is created on demand just for this job and then decommissioned afterwards.
Does your used AWS IAM account have the right permissions? Due to this process we of course need to be able to configure a new instance and all the security stuff around it. Check the Required Permissions for a special section on “Amazon S3 Glacier Storage Permissions” for a C&P version of the required IAM policy.
And of course you have to double check whether it’s possible at all to connect to the provisioned EC2 instance via SSH from the VBR with the configured settings (VPC/subnet/security group) - check the Used Ports section for the Proxy Appliance - it requires a connection via SSH (TCP/22) and HTTPS (TCP/443).
I assume it’s just the missing ports in the SG or maybe a limitation of the network ACL.
I guess it is tcp/22 i will check this.
Hi Hartmut,
we do need an appliance to convert from the “normal” S3 objects to the bigger archive objects. This appliance is created on demand just for this job and then decommissioned afterwards.
Does your used AWS IAM account have the right permissions? Due to this process we of course need to be able to configure a new instance and all the security stuff around it. Check the Required Permissions for a special section on “Amazon S3 Glacier Storage Permissions” for a C&P version of the required IAM policy.
And of course you have to double check whether it’s possible at all to connect to the provisioned EC2 instance via SSH from the VBR with the configured settings (VPC/subnet/security group) - check the Used Ports section for the Proxy Appliance - it requires a connection via SSH (TCP/22) and HTTPS (TCP/443).
I assume it’s just the missing ports in the SG or maybe a limitation of the network ACL.
It is TCP/22. I found the suitable Veeam logfiles. Thx to you.
