We are always trying to stay on top of the new functionality introduced by Amazon. In this guide, we will describe how to create and access Amazon S3 endpoint in your VPC.
Amazon Virtual Private Cloud (Amazon VPC) is the Amazon service that allows you to create and manage virtual private networks. By default, all AWS resources are accessed via the public Internet. You may need to restrict access to your cloud network due to security requirements of your project. Before now, you had to allow internet communications between your VPC and AWS resources that you need. The recently introduced feature called VPC Endpoints allows you to keep your VPC truly private and grant access only to the resources that you need directly from the network itself.
Moving Amazon EC2 instance to another Availability Zone, VPC or AWS Region may result in a headache for administrators, who think that it is a must to stop the existing and brand a new instance each time. If it’s a production instance, the interruption disrupts the working process and leads to the significant money/time losses. So, do you really have to migrate all data manually?
The answer is “no”, if you know how to properly use AWS native tools. In this article we explain how to easily move working Amazon EC2 instance to a different Availability Zone, VPC or AWS Region.
Let’s get started from the step one.
As you may know, one of the leaders on the cloud market, Amazon company, offers Amazon Virtual Private Cloud (VPC). It is an isolated AWS segment which represents a virtual network managed by your team. Now it is fully supported by Cloudberry Drive.
Here you will find a brief feature explanation and guidelines how to connect your Amazon VPC to Cloudberry Drive.