Amazon Web Services has indicated that it is still concerned about the misconfigured segments in its Simple Storage Service (S3) when creating one of the tools to manage them for free.
AWS suffered last year after a series of data leaks caused by customers who had incorrectly configured their S3 storage.
It is an easy mistake to make because the routine to build a new segment offers the possibility of establishing policies from an existing segment. Forget the settings on an old one and, pow, your things could be online. Or you can press the "Manage public permissions" dialog box with your thumb and choose the unsafe option.
Regardless of why naked and solitary cubes are left on the Internet, AWS was ashamed to associate with careless users and last year provided the world with a tool that issued orange alerts when unsafe buckets contaminated users' AWS fleets.
Now the company has decided that the version of that tool included in its Trusted Advisor service should be free.
"Previously available only for business and enterprise support customers, this verification identifies S3 buckets that are public access due to ACL or policies that allow read / write access for any user," said the colossus clouded.
Since the original tool was not much more than a yellow light in an administration console, making it more widely available for free can not prevent the tide of poorly constructed cubes. But at least AWS can say that it is trying to help ...
Monday, February 26, 2018
Sunday, February 18, 2018
Amazon overtakes Microsoft in market capitalisation, thanks to booming AWS revenue
Amazon is officially the third most valuable company in the United States.
The retail giant surpassed Microsoft's market capitalization for the first time on Wednesday, reaching $ 702.5 billion.
Amazon and Microsoft are leaders in their respective industries - Microsoft in Office and Productivity Software and Amazon in Retail. But the two companies are in direct competition in the cloud and the business sector is booming for both companies.
Amazon earlier this month reported financials on its activities in the cloud for the first time. Amazon Web Services reported revenue of $ 17.4 billion in 2017, an increase of 43% from $ 12.2 billion in 2016.
At the same time, Microsoft said Azure's year-on-year sales rose 98 percent and its revenue was from "smart cloud," a segment comprising Azure, of $ 7.8 billion last quarter.
The Amazon, meanwhile, has almost quadrupled in value over the past three years. The company has allocated 10% of the total revenue to AWS.
Amazon's market capitalization was 702.5 billion US dollars on Wednesday night; Shares of the company traded US $ 8.65 (0.6%) to US $ 1459.70 late Thursday. Microsoft was worth $ 699.2 billion after the market closed on Wednesday.
Amazon is still behind Apple, with a value of US $ 849,200,000,000, and the alphabet, Google's parent company, which is US $ 744,800,000,000 on Wednesday. Microsoft is currently in fourth place.
At the end of the market on Wednesday, CNBC named Amazon CEO Jeff Bezos, the richest man of all time, beating Microsoft founder Bill Gates, who had an estimated US $ 100 billion fortune in 1999. Bezos owns 78.9 million shares of Amazon stock, and currently has an estimated net worth of US $ 118 billion, according to the Bloomberg Billionaire index.
The retail giant surpassed Microsoft's market capitalization for the first time on Wednesday, reaching $ 702.5 billion.
Amazon and Microsoft are leaders in their respective industries - Microsoft in Office and Productivity Software and Amazon in Retail. But the two companies are in direct competition in the cloud and the business sector is booming for both companies.
Amazon earlier this month reported financials on its activities in the cloud for the first time. Amazon Web Services reported revenue of $ 17.4 billion in 2017, an increase of 43% from $ 12.2 billion in 2016.
At the same time, Microsoft said Azure's year-on-year sales rose 98 percent and its revenue was from "smart cloud," a segment comprising Azure, of $ 7.8 billion last quarter.
The Amazon, meanwhile, has almost quadrupled in value over the past three years. The company has allocated 10% of the total revenue to AWS.
Amazon's market capitalization was 702.5 billion US dollars on Wednesday night; Shares of the company traded US $ 8.65 (0.6%) to US $ 1459.70 late Thursday. Microsoft was worth $ 699.2 billion after the market closed on Wednesday.
Amazon is still behind Apple, with a value of US $ 849,200,000,000, and the alphabet, Google's parent company, which is US $ 744,800,000,000 on Wednesday. Microsoft is currently in fourth place.
At the end of the market on Wednesday, CNBC named Amazon CEO Jeff Bezos, the richest man of all time, beating Microsoft founder Bill Gates, who had an estimated US $ 100 billion fortune in 1999. Bezos owns 78.9 million shares of Amazon stock, and currently has an estimated net worth of US $ 118 billion, according to the Bloomberg Billionaire index.
Monday, February 5, 2018
Learn these AWS basics before you run VMware on AWS
There are a few things that every vSphere administrator needs to know before attempting to run VMware on AWS, including how VPCs work and how AWS handles resource provisioning.
Familiarize yourself with these basic Amazon Web Services concepts, including VPC and how AWS handles resources, before attempting to run VMware on AWS.
Now that VMware Cloud on AWS is available, vSphere administrators need to become familiar with how Amazon Web Services works to run VMware on AWS.
VMware Cloud on AWS is an on-demand service that ensures that the datacenter (SDDC) defined by VMware software can be run directly on the AWS Cloud. VMware provides vSphere, vSAN, NSX and vCenter management, as well as support, while Amazon provides the elastic-metal infrastructure and additional components. Provided correctly configured, VMware tools such as vRealize Automation can use standard AWS resources.
This setup is transparent for the VMware Cloud on AWS administrator; VMware implements its SDDC in a "shadow" Virtual Private Cloud (VPC) that the customer does not see. For the vSphere administrator, the VMware management system appears in the same way as in the datacenter.
Although VMware abstracts a large part of the complexity of AWS, it is still in the interest of vSphere admin to become familiar with some AWS basics.
AWS VPC architecture for beginners
To run VMware on AWS, AWS uses its VPC to provide a logically isolated part of the AWS Cloud where you can start AWS components.
A VPC is a software-defined network that contains all network-related functions of AWS. The AWS administrator configures and manages access to everything in the AWS VPC architecture, although he can use AWS Identity Access and Management (IAM) service to delegate this responsibility to other administrators. It's a good practice to create subordinate IAM user accounts for daily work in the VPC instead of using the primary administrator account.
Each VPC lives in a region, a cluster of highly redundant data centers that function as a single logical group. To use a VPC, the AWS administrator must first select a region and then define the VPC. VPCs can not be distributed across different regions, but one of the advantages of the AWS VPC architecture is that you can have multiple VPCs within a single region. The use of multiple VPCs makes management easier because it can logically isolate the infrastructure. This allows multiple customers to live within one account while maintaining privacy and isolation.
AWS command structure
Each AWS customer has a root user account, which is managed at AWS account level. The root user account has access to identity and access management and can generate new resources, create subordinate user accounts, and defer responsibilities to these subordinate accounts as needed. By default, subordinate accounts do not have any rights within the infrastructure until an AWS administrator assigns rights to them.
If you log in to the root account, you'll see that there are different sizes and types of VMs - which AWS refers to copies - that you can use. Elastic block storage is the basis of these VMs.
Note that AWS sources do not offer the option to define VM sizes; instead AWS uses the dimensioning of instances, which means that the administrator can only use the sizes offered by Amazon. If the server usage becomes too large for the dimensioning, the administrator can scale this up to a higher level of CPU, RAM and so on. Scaling is a quick solution, but requires downtime and is limited to the resources that AWS offers.
AWS offers various images from which the administrator can use sources. It is also possible to create highly customized images, which can be useful in a larger implementation. A new AWS setting also requires the administrator to choose a region in which he places his resources. It is important to choose the right region because different regions have different cost implications.
In summary, to run VMware on AWS, the vSphere administrator has two ways to use AWS and use AWS resources directly: vRealize and VMC on AWS. With VMC on AWS, the vSphere administrator can easily access the VMC on the AWS console, create an SDDC and get a vCenter login and continue creating VMs as usual .
Familiarize yourself with these basic Amazon Web Services concepts, including VPC and how AWS handles resources, before attempting to run VMware on AWS.
Now that VMware Cloud on AWS is available, vSphere administrators need to become familiar with how Amazon Web Services works to run VMware on AWS.
VMware Cloud on AWS is an on-demand service that ensures that the datacenter (SDDC) defined by VMware software can be run directly on the AWS Cloud. VMware provides vSphere, vSAN, NSX and vCenter management, as well as support, while Amazon provides the elastic-metal infrastructure and additional components. Provided correctly configured, VMware tools such as vRealize Automation can use standard AWS resources.
This setup is transparent for the VMware Cloud on AWS administrator; VMware implements its SDDC in a "shadow" Virtual Private Cloud (VPC) that the customer does not see. For the vSphere administrator, the VMware management system appears in the same way as in the datacenter.
Although VMware abstracts a large part of the complexity of AWS, it is still in the interest of vSphere admin to become familiar with some AWS basics.
AWS VPC architecture for beginners
To run VMware on AWS, AWS uses its VPC to provide a logically isolated part of the AWS Cloud where you can start AWS components.
A VPC is a software-defined network that contains all network-related functions of AWS. The AWS administrator configures and manages access to everything in the AWS VPC architecture, although he can use AWS Identity Access and Management (IAM) service to delegate this responsibility to other administrators. It's a good practice to create subordinate IAM user accounts for daily work in the VPC instead of using the primary administrator account.
Each VPC lives in a region, a cluster of highly redundant data centers that function as a single logical group. To use a VPC, the AWS administrator must first select a region and then define the VPC. VPCs can not be distributed across different regions, but one of the advantages of the AWS VPC architecture is that you can have multiple VPCs within a single region. The use of multiple VPCs makes management easier because it can logically isolate the infrastructure. This allows multiple customers to live within one account while maintaining privacy and isolation.
AWS command structure
Each AWS customer has a root user account, which is managed at AWS account level. The root user account has access to identity and access management and can generate new resources, create subordinate user accounts, and defer responsibilities to these subordinate accounts as needed. By default, subordinate accounts do not have any rights within the infrastructure until an AWS administrator assigns rights to them.
If you log in to the root account, you'll see that there are different sizes and types of VMs - which AWS refers to copies - that you can use. Elastic block storage is the basis of these VMs.
Note that AWS sources do not offer the option to define VM sizes; instead AWS uses the dimensioning of instances, which means that the administrator can only use the sizes offered by Amazon. If the server usage becomes too large for the dimensioning, the administrator can scale this up to a higher level of CPU, RAM and so on. Scaling is a quick solution, but requires downtime and is limited to the resources that AWS offers.
AWS offers various images from which the administrator can use sources. It is also possible to create highly customized images, which can be useful in a larger implementation. A new AWS setting also requires the administrator to choose a region in which he places his resources. It is important to choose the right region because different regions have different cost implications.
In summary, to run VMware on AWS, the vSphere administrator has two ways to use AWS and use AWS resources directly: vRealize and VMC on AWS. With VMC on AWS, the vSphere administrator can easily access the VMC on the AWS console, create an SDDC and get a vCenter login and continue creating VMs as usual .
Subscribe to:
Posts (Atom)