Is it possible to create such a SCP (Service Control Policy) and attach it to account which denies any new resources (infrastructure) launching within this account? Assuming that the account is part of AWS Organizations.
The question arises from the following confusions:
Yes, it is possible to do.
SCP can contain explicit deny rules, for example deny creation of any EC2-related instances and resources:
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Statement1",
"Effect": "Deny",
"Action": [
"ec2:Create*"
],
"Resource": "*"
}
]
}
Any SCP can be attached to: