AWS (Glue / EMR) — AWS Marketplace or private S3

1. Prepare and approve the AWS release

1. Verify the customer or listing authorization, commercial agreement/order, version, AWS Regions, accounts, Glue/EMR runtime versions, Java/Scala/Spark compatibility, and support responsibilities.
2. Obtain DataAIETL-AWS-1.0.0.zip and ARTIFACTS.sha256. Recompute all hashes and validate the JARs on the claimed AWS Spark runtime.
3. Review the container assets separately if pursuing Marketplace. Build from pinned approved inputs, scan the image and dependencies, and ensure no credentials, customer data, development licenses, or unnecessary tools are included.
4. Create a release record with version, hashes/image digest, customer or offer ID, regions, approvers, agreement/order reference, test results, and rollback owner.

2A. Fulfill through private S3

1. Create or select a private S3 bucket and customer-specific prefix in the approved AWS account/Region. Keep S3 Block Public Access enabled and require encryption and TLS.
2. Upload the immutable production ZIP and checksum manifest. Enable versioning/object retention according to release policy.
3. Prefer cross-account IAM access for recurring licensed use: grant only the authorized customer role s3:GetObject on the exact versioned prefix and required KMS permissions.
4. For a one-time download, create a presigned URL with the shortest practical lifetime. Treat the URL as a bearer credential and send it only to the approved customer contact.
5. Test from a customer-equivalent role or clean session: download the ZIP and checksum, recompute SHA-256, extract, and attach the JARs to an isolated Glue/EMR job.
6. Give the customer exact S3 object/version or presigned link, filename/hash, supported runtimes, IAM/KMS requirements, production guides, license/order reference, and support path.
7. Remove the cross-account grant or allow the presigned URL to expire when entitlement ends; confirm there is no public ACL or bucket policy.

2B. Create an AWS Marketplace product

1. Register Yanbor LLC as an AWS Marketplace seller and complete business, tax, banking, seller-profile, agreement, and access requirements in the current AWS seller workflow.
2. Select a supported product type that matches the deliverable. For the supplied container assets, use a container product only after the container is actually runnable and validated for the documented customer workflow.
3. Create the product record and obtain its product ID/product code. Use the AWS-owned Marketplace ECR repository and upload only the reviewed image/digest as instructed by AWS.
4. Complete vulnerability scanning and remediate blocking findings. Validate startup, configuration, logging, least-privilege IAM, networking, license enforcement/entitlement, upgrade, and uninstall/termination behavior.
5. Prepare title, descriptions, categories, logo, architecture, deployment instructions, supported Regions/services, pricing model, refund policy, EULA, privacy policy, support/SLA, usage dimensions, and required customer permissions.
6. Configure Marketplace pricing and metering/contract integration appropriate to the product. Do not advertise external commercial fulfillment that conflicts with AWS Marketplace policy.
7. Add a product version and deployment option, then test it while the listing has limited visibility using authorized test accounts.
8. Submit the listing and required change requests for AWS review. Resolve technical, security, content, and policy findings; preserve the exact image digest reviewed.
9. After approval, request public visibility and verify subscription, entitlement, deployment, metering, documentation, and support. Do not call it available until the live flow succeeds.
10. Use AWS private offers only when the product type and seller/listing status meet AWS requirements. Define buyer account, pricing, duration, terms, expiration, and verify the generated offer URL before sending it.

3. Maintain and withdraw releases

• Use a new immutable ZIP/version and container image digest for updates; never replace reviewed bytes.
• Repeat Glue/EMR compatibility, security scan, clean deployment, entitlement, and output tests.
• Follow AWS Marketplace change-request and customer-notification rules for new versions or restrictions.

Official references

• AWS: register as a Marketplace seller
• AWS: container product lifecycle
• AWS: create a private offer
• AWS: share a private S3 object with a presigned URL

Back to DataAI ETL Markets