When calling AWS APIs, the resource type is generally the noun in the operation name, e.g.
AWSĪWS Resources are the objects that get created when the respective AWS APIs are called – continuing our long running example with EC2 – when performing an API call to the RunInstances (or `aws ec2 run-instances` if you prefer the AWS CLI) operation, a resource of type EC2 instance is created with the specified parameters, such as AMI, region, availability zone (AZ) or subnet ID. In the 3 rd blog of this series, we’ll look at the “What” – resources, their structure and organization, for the big three cloud providers – AWS, Azure and Google Cloud.
#List stack resources series#
The second post in the series covered – what permissions exist in each provider, or “How” these permissions are structured and how they get assigned to principals. This journey started with a blog post focused on what types of principals exist in each provider and was accompanied by a quick overview of the organization of these principals and the authentication mechanics, or for short – the “Who” part of the IAM equation.
Welcome to the third part of the blog series on comparing (Identity and Access Management) IAM and Security Models for the “Big Three” public cloud providers.
0 kommentar(er)
