Lists all of the available actions, resources, and condition context keys that can be used in IAM policies to control access to AWS services.| docs.aws.amazon.com
How an event notification message for Amazon S3 is structured.| docs.aws.amazon.com
Learn the difference between identity-based policies and resource-based policies.| docs.aws.amazon.com
This section covers authorization (using RBAC) of your lakeFS server.| lakeFS Documentation
Before you use IAM to manage access to Amazon S3, learn what IAM features are available to use with Amazon S3. Identity-based policies Yes Resource-based policies Yes Policy actions Yes Policy resources Yes Policy condition keys (service-specific)| docs.aws.amazon.com
Learn how to configure Amazon S3 replication when the source and destination buckets are owned by different AWS accounts.| docs.aws.amazon.com
Use the IAM policy simulator to test and troubleshoot IAM policies that are attached to users, IAM groups, roles, or resources.| docs.aws.amazon.com
Public disclosure of a vulnerability in AWS Amplify which exposed IAM roles associated with Amplify projects to be assumed by anyone in the world.| securitylabs.datadoghq.com
Describes the Principal element of the AWS JSON policy language.| docs.aws.amazon.com
Learn the relationship of IAM users to credentials, permissions, and AWS accounts.| docs.aws.amazon.com
A few years ago, I wrote about determining AWS account IDs from AWS access keys, i.e. those strings that begin with AKIA or ASIA. It’s also possible to determine information from other AWS IAM unique IDs, specifically these two from the table in Amazon’s docs.| Aidan Steele’s blog (usually about AWS)
Describes each of the AWS global condition keys available to use in IAM policies.| docs.aws.amazon.com
)
+ tl;dr - Steps on how to set up SES with Pulumi (their brand new logo is the one above), an infrastructure-as-code (written in code) solution. Skip to the end for all the code, all at once UPDATE (08/16/2021) SES no longer requires separate domain identitify verification -- this is now integrated with the DKIM records you build for SES. You do not need the aws.ses.DomainIdentityVerification Pulumi object at all anymore -- the post has been updated to reflect that.| vadosware.io