Official Media2Cloud template broken for new accounts due to deprecated AppRegistry

This is expected fallout from the AppRegistry change, not anything specific to your account. As of July 30, 2026, AWS Service Catalog AppRegistry stopped accepting new customers — accounts that never used it can't create AWS::ServiceCatalogAppRegistry::* resources, which is exactly the 403 you're hitting. Accounts that already used AppRegistry keep working, which is why this doesn't reproduce everywhere. Background: AWS Service Catalog AppRegistry availability change.

On your two questions:

Timeline / updated template URL: there isn't a published fix I can point you to. The template still hardcodes the three AppRegistry resources, and there's no tracking issue for this in the repo yet. Since this reproduces for every new account, it's worth reporting so the maintainers can make AppRegistry optional — that's the supported feedback path for AWS Guidance solutions. Open an issue at guidance-for-media2cloud-on-aws/issues and include the full error, the affected resources, and the July 30, 2026 cause so it's unambiguous.

Unblocking yourself now: the AppRegistry pieces are metadata-only — they group the stack's resources for management/cost visibility and don't drive any Media2Cloud functionality (ingest, analysis, web UI). You can build and deploy your own copy of the template without them. The repo already has the build tooling for this (README → "Building Media2Cloud V4 on your environment"):

1. Clone the repo.
2. In the template, gate the three resources — AWS::ServiceCatalogAppRegistry::Application, ...::ResourceAssociation, and ...::AttributeGroupAssociation — behind a Condition tied to a new parameter (e.g. DeployAppRegistry, default false), rather than deleting them outright. A condition keeps the template reusable on both old and new accounts, and is a cleaner diff to hand back to the maintainers in your issue/PR.
3. Remove or condition anything that references those logical IDs too — DependsOn, Ref/Fn::GetAtt, and any Outputs — otherwise CloudFormation fails validation on the dangling references.
4. Build with deployment/build-s3-dist.sh (assign a unique --version so stack updates behave), then deploy the artifacts to your own S3 bucket and create the stack from your media2cloud.template URL.

You lose only the AppRegistry application grouping — which you can't create on a new account anyway. If you want that grouping back, the documented no-cost alternatives are tags + AWS Resource Groups / Resource Explorer.

If you have an existing account that already used AppRegistry, deploying the stock template there will succeed — useful as a quick stopgap, but the template edit above is the real fix for new accounts.

The issue you're encountering is due to AWS Service Catalog AppRegistry transitioning to maintenance mode and no longer being available to new customers as of July 30, 2026. Since you're deploying into a new testing account, you don't have legacy access to AppRegistry, which is why the CloudFormation stack creation fails with a 403 error on the AppRegistry resources.

Regarding your questions about when the Media2Cloud template will be updated and whether there's an alternative template available, I don't have specific information about the AWS Solutions team's timeline for updating the Media2Cloud template or an alternative official template URL that addresses this AppRegistry issue.

For your immediate needs, you have a few options to consider:

1. You could modify the CloudFormation template yourself to remove the AppRegistry-related resources (AWS::ServiceCatalogAppRegistry::Application, ResourceAssociation, and AttributeGroupAssociation). The core Media2Cloud functionality should work without these components, as AppRegistry primarily provides resource organization and metadata management capabilities.

2. For the organizational and tagging capabilities that AppRegistry provided, you can use alternative AWS services at no additional cost: AWS Tagging for assigning metadata to resources, AWS Resource Groups for creating permanent named groupings based on tags within a single Region, and AWS Resource Explorer for cross-Region and cross-account resource discovery.

For the most current information about template updates or official guidance on deploying Media2Cloud in new accounts, I recommend reaching out through the AWS Support Center at https://console.aws.amazon.com/support/ to inquire about the solution's roadmap and any available workarounds.
Sources
AWS Service Catalog AppRegistry availability change - AWS Service Catalog AppRegistry

Hi everyone,

I wanted to post a quick update and say a huge thank you to everybody who chimed in to help with this, especially Taka and Riku_Kobayashi. I really appreciate your time and assistance!

The good news is that the issue has been resolved. A huge shoutout to aws-kens, who fixed the AppRegistry dependency issue on GitHub (#184) and officially updated the Media2Cloud template to version 4.0.11.

Because of this update, the deployment is now fully working out-of-the-box, even if you are using a brand-new AWS account set up after the July 30th AppRegistry cutoff date.

Thanks again, everyone!