⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Platform Engineering & IDP Interview Questions Scenario 33 of 50 in Platform Engineering & IDP
Senior Platform Engineer Platform Engineering Control Planes & Crossplane Cloud Vending
🎯 Target Role / Context: Senior Platform Engineer Interview · Cloud Governance & Storage

Q: Developers create S3 buckets manually, often forgetting SSE-KMS encryption, omitting public access blocks, and leaving terabytes of unexpiring logs that inflate cloud bills. How do you build a Crossplane self-service bucket vending system that guarantees compliance by design?

Designing an enterprise Crossplane Composition vending AWS S3 buckets with mandatory KMS encryption, blocked public access, and automated lifecycle rules.

#Platform Engineering #Crossplane #AWS S3 #Security #FinOps #Self-Service
🎙️ Candidate Opening & Architectural Context
"Manual cloud storage provisioning guarantees security breaches and cost leaks. By creating a Crossplane AppStorage composite resource, the platform team enforces KMS encryption, 100% public access blocking, and automated intelligent-tiering lifecycle transitions at the composition layer."
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: Manual cloud storage provisioning guarantees security breaches and cost leaks. By creating a Crossplane AppStorage composite resource, the platform team enforces KMS encryption, 100% public access blocking, and automated intelligent-tiering lifecycle transitions at the composition layer.

1

Define Minimal XRD Developer Interface

Expose only developer-relevant fields: bucket purpose, retention days, and lifecycle tiering.

apiVersion: apiextensions.crossplane.io/v1
kind: CompositeResourceDefinition
metadata:
  name: xappstorages.platform.acme.com
spec:
  group: platform.acme.com
  names: { kind: XAppStorage, plural: xappstorages }
  claimNames: { kind: AppStorage, plural: appstorages }
  versions:
    - name: v1alpha1
      schema:
        openAPIV3Schema:
          type: object
          properties:
            spec:
              properties:
                lifecycleDays: { type: integer, default: 90 }
                enableVersioning: { type: boolean, default: true }
2

Enforce Mandatory Security and FinOps in Crossplane Composition

The Composition renders an AWS S3 Bucket, PublicAccessBlock, ServerSideEncryptionConfiguration, and LifecycleConfiguration automatically.

# Composition resource snippet
- name: s3-public-access-block
  base:
    apiVersion: s3.aws.upjet.crossplane.io/v1beta1
    kind: BucketPublicAccessBlock
    spec:
      forProvider:
        blockPublicAcls: true
        blockPublicPolicy: true
        ignorePublicAcls: true
        restrictPublicBuckets: true
Advertisement
3

Export Read/Write IAM Policy to Developer Namespace

Crossplane generates a scoped IAM policy granting read/write access to that specific bucket ARN only, exporting the policy ARN to a Kubernetes Secret in the developer's namespace.

Pro Tip: Compliance by Design: Developers cannot misconfigure security because the Composition does not expose options to disable encryption or public access blocks.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Use Crossplane compositions to vend S3 storage with mandatory KMS encryption, strict public access blocks, and automated lifecycle transitions enforced by default."
⚡ 60-Second Elevator Pitch Talking Points
  • Design Crossplane XRDs exposing minimal storage parameters while hiding cloud configuration complexity.
  • Hardcode PublicAccessBlock and ServerSideEncryptionConfiguration inside the central Composition.
  • Automatically vend scoped IAM policies granting developers access strictly to their own provisioned bucket.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Relying on legacy bucket ACLs instead of modern S3 Block Public Access and IAM bucket policies when configuring Self Service Bucket AWS recommends disabling ACLs (Bucket Owner Enforced) in favor of centralized declarative bucket policies and account-level Block Public Access controls.
  2. Confusing SSE-S3 encryption with KMS customer-managed key (SSE-KMS) authorization policies when configuring Self Service Bucket Accessing SSE-KMS encrypted objects requires both s3:GetObject and kms:Decrypt permissions; neglecting KMS key policies causes silent 403 Forbidden errors.
  3. Using sequential timestamps or predictable prefixes for high-throughput S3 read and write keys when configuring Self Service Bucket Sequential key prefixes limit S3 horizontal partitioning; randomized hash prefixes distribute workloads across partitions to achieve 3,500 PUT and 5,500 GET requests/sec.
  4. Failing to audit S3 object delete markers when troubleshooting missing versioned objects when configuring Self Service Bucket Issuing a DELETE on a versioned bucket only adds a delete marker; engineers must retrieve previous versions or purge markers to restore data.
Advertisement
Want more Platform Engineering & IDP scenarios?
Explore our complete collection of scenario-based Platform Engineering & IDP interview runbooks.
Browse All Platform Engineering & IDP Questions →