Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: rds.aws.upbound.io Cluster created failed #1668

Open
1 task done
philipphomberger opened this issue Feb 5, 2025 · 0 comments
Open
1 task done

[Bug]: rds.aws.upbound.io Cluster created failed #1668

philipphomberger opened this issue Feb 5, 2025 · 0 comments
Labels
bug Something isn't working needs:triage

Comments

@philipphomberger
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

I get this error always than I try to create a RDS Cluster.
I have no problems to create GlobalCluster Ressourcen.

apiVersion: rds.aws.upbound.io/v1beta2
kind: Cluster

Message: async create failed: failed to create the resource: [{0 creating RDS Cluster (example3): operation error RDS: CreateDBCluster, https response error StatusCode: 403, RequestID: xxxxxxxxxxxxxxx, api error AccessDenied: User: arn:aws:iam::xxxxxxxxxxxxxx:user/crossplane-demo is not authorized to perform: rds:CreateDBCluster on resource: arn:aws:rds:us-west-1:xxxxxxxxx:cluster:example3 with an explicit deny in a service control policy []}]

The User have Admin Access.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "*",
            "Resource": "*"
        }
    ]
}

To be save that I have no Access Issues.

Other Resources Like Buckets, VPC, GlobalCluster working well.

Thank you.

Resource MRs required to reproduce the bug

Create a Cluster:

apiVersion: rds.aws.upbound.io/v1beta1
kind: Cluster
metadata:
  annotations:
    meta.upbound.io/example-id: rds/v1beta1/cluster
  name: example-kms-cluster
spec:
  forProvider:
    autoGeneratePassword: true
    engine: aurora-postgresql
    masterPasswordSecretRef:
      key: password
      name: sample-cluster-password
      namespace: crossplane-system
    masterUsername: cpadmin
    region: eu-west-1
    skipFinalSnapshot: true
  writeConnectionSecretToRef:
    name: sample-rds-cluster-secret
    namespace: crossplane-system
apiVersion: rds.aws.upbound.io/v1beta2
kind: Cluster
metadata:
  annotations:
    meta.upbound.io/example-id: rds/v1beta2/cluster
  name: example3
spec:
  forProvider:
    autoGeneratePassword: true
    engine: aurora-postgresql
    masterPasswordSecretRef:
      key: password
      name: sample-cluster-password
      namespace: crossplane-system
    masterUsername: cpadmin
    region: eu-west-1
    skipFinalSnapshot: true
  writeConnectionSecretToRef:
    name: sample-rds-cluster-secret
    namespace: crossplane-system

Steps to Reproduce

Install actual Version of Crossplane and try to create RDS Cluster Ressource.

What happened?

Message: async create failed: failed to create the resource: [{0 creating RDS Cluster (example3): operation error RDS: CreateDBCluster, https response error StatusCode: 403, RequestID: xxxxxxxxxxxxxxx, api error AccessDenied: User: arn:aws:iam::xxxxxxxxxxxxxx:user/crossplane-demo is not authorized to perform: rds:CreateDBCluster on resource: arn:aws:rds:us-west-1:xxxxxxxxx:cluster:example3 with an explicit deny in a service control policy []}]

Relevant Error Output Snippet

Message:               async create failed: failed to create the resource: [{0 creating RDS Cluster (example3): operation error RDS: CreateDBCluster, https response error StatusCode: 403, RequestID: xxxxxxxxxxxxxxx, api error AccessDenied: User: arn:aws:iam::xxxxxxxxxxxxxx:user/crossplane-demo is not authorized to perform: rds:CreateDBCluster on resource: arn:aws:rds:us-west-1:xxxxxxxxx:cluster:example3 with an explicit deny in a service control policy  []}]

Crossplane Version

1.18.2

Provider Version

v1

Kubernetes Version

1.31.2

Kubernetes Distribution

Gardener Cluster in AWS

Additional Info

No response

@philipphomberger philipphomberger added bug Something isn't working needs:triage labels Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs:triage
Projects
None yet
Development

No branches or pull requests

1 participant