#AwsResourceAccessManager
AWS Elemental MediaConnect Router now supports endpoint connection management

https://aws.amazon.com/mediaconnect/features/router/ now supports managing external connections through a new endpoint registry. The registry provides a central...

#AWS #AwsResourceAccessManager #AwsElementalMediaconnect
AWS Elemental MediaConnect Router now supports endpoint connection management
https://aws.amazon.com/mediaconnect/features/router/ now supports managing external connections through a new endpoint registry. The registry provides a centralized interface to register and manage both standard endpoints—devices or software outside the service, such as cameras, sources, monitors, and other destinations—and connections to other AWS accounts. You can share registered endpoints directly with other AWS accounts, streamlining cross-account live video workflows.  Cross-account endpoint sharing lowers costs by reducing required compute instances and decreases latency through fewer network hops when sharing live content across AWS accounts.. It also eliminates the need to manually chain router inputs and outputs, coordinate IP addresses out of band, and manage connection security. The endpoint registry gives you a single interface to manage all external connections to MediaConnect for seamless integration with your existing infrastructure. You get cross-account sharing through AWS Resource Access Manager (AWS RAM), transparent verification of encryption and protocol controls, and built-in connection management with Connection Manager. Use cases include content distributors sharing live feeds with downstream partners, broadcasters collaborating across organizational boundaries, and media workflows that require secure cross-account video transport. MediaConnect endpoint registry is available in all AWS Regions where AWS Elemental MediaConnect Router is available, at no additional cost. For more information, see the AWS Elemental MediaConnect https://docs.aws.amazon.com/mediaconnect/latest/ug/working-with-endpoints.html.
aws.amazon.com
October 27, 2026 at 7:05 PM
🆕 AWS Elemental MediaConnect Router now supports endpoint registry for managing external connections, reducing costs and simplifying live video workflows with cross-account sharing and secure transport, available at no extra cost.

#AWS #AwsResourceAccessManager #AwsElementalMediaconnect
AWS Elemental MediaConnect Router now supports endpoint connection management
AWS Elemental MediaConnect Router now supports managing external connections through a new endpoint registry. The registry provides a centralized interface to register and manage both standard endpoints—devices or software outside the service, such as cameras, sources, monitors, and other destinations—and connections to other AWS accounts. You can share registered endpoints directly with other AWS accounts, streamlining cross-account live video workflows.  Cross-account endpoint sharing lowers costs by reducing required compute instances and decreases latency through fewer network hops when sharing live content across AWS accounts.. It also eliminates the need to manually chain router inputs and outputs, coordinate IP addresses out of band, and manage connection security. The endpoint registry gives you a single interface to manage all external connections to MediaConnect for seamless integration with your existing infrastructure. You get cross-account sharing through AWS Resource Access Manager (AWS RAM), transparent verification of encryption and protocol controls, and built-in connection management with Connection Manager. Use cases include content distributors sharing live feeds with downstream partners, broadcasters collaborating across organizational boundaries, and media workflows that require secure cross-account video transport. MediaConnect endpoint registry is available in all AWS Regions where AWS Elemental MediaConnect Router is available, at no additional cost. For more information, see the AWS Elemental MediaConnect User Guide.
aws.amazon.com
October 27, 2026 at 7:10 PM
🆕 AWS Systems Manager now shares SSM Documents with entire orgs/OUs via AWS RAM, simplifying access and eliminating manual updates. Available in all regions, no extra charge. For details, see the User Guide.

#AWS #AwsSystemsManager #AwsResourceAccessManager
AWS Systems Manager now supports sharing documents through AWS Resource Access Manager
AWS Systems Manager now lets you share your Systems Manager Documents (SSM Documents) with an entire AWS organization or with specific organizational units (OUs) using AWS Resource Access Manager (AWS RAM). Previously, you could only share a document publicly or with a list of individual account IDs. You can now easily share a document with your organization or OUs, and Systems Manager automatically keeps that sharing up to date as accounts are added to or removed from your organization or OU, so you no longer need to track and update accounts manually. To share a document, you create an AWS RAM resource share, add the SSM Documents you want to share, and select the organizations or OUs to share them with. Because sharing is managed through AWS RAM and resource-based policies, access is granted through standard AWS authorization. When you share a document with an account outside your organization, that account receives a resource share invitation and gains access only after it accepts, giving both the document owner and the consumer more control over shared access. This capability is available in the Systems Manager console, the AWS Command Line Interface (AWS CLI), and the AWS SDKs, in all AWS Regions where AWS Systems Manager is available. There is no additional charge to share documents through AWS RAM. To get started, open the Documents page in the Systems Manager console, or see the AWS Systems Manager User Guide at https://docs.aws.amazon.com/systems-manager/latest/userguide/documents-ssm-sharing.html.
aws.amazon.com
September 29, 2026 at 4:10 PM
AWS Systems Manager now supports sharing documents through AWS Resource Access Manager

AWS Systems Manager now lets you share your Systems Manager Documents (SSM Documents) with an entire AWS organization or with specific organizational units (O...

#AWS #AwsSystemsManager #AwsResourceAccessManager
AWS Systems Manager now supports sharing documents through AWS Resource Access Manager
AWS Systems Manager now lets you share your Systems Manager Documents (SSM Documents) with an entire AWS organization or with specific organizational units (OUs) using AWS Resource Access Manager (AWS RAM). Previously, you could only share a document publicly or with a list of individual account IDs. You can now easily share a document with your organization or OUs, and Systems Manager automatically keeps that sharing up to date as accounts are added to or removed from your organization or OU, so you no longer need to track and update accounts manually. To share a document, you create an AWS RAM resource share, add the SSM Documents you want to share, and select the organizations or OUs to share them with. Because sharing is managed through AWS RAM and resource-based policies, access is granted through standard AWS authorization. When you share a document with an account outside your organization, that account receives a resource share invitation and gains access only after it accepts, giving both the document owner and the consumer more control over shared access. This capability is available in the Systems Manager console, the AWS Command Line Interface (AWS CLI), and the AWS SDKs, in all AWS Regions where AWS Systems Manager is available. There is no additional charge to share documents through AWS RAM. To get started, open the Documents page in the Systems Manager console, or see the AWS Systems Manager User Guide at https://docs.aws.amazon.com/systems-manager/latest/userguide/documents-ssm-sharing.html.
aws.amazon.com
September 29, 2026 at 4:05 PM
AWS Resource Access Manager (RAM) now supports Internet Protocol Version 6 (IPv6)

AWS Resource Access Manager (AWS RAM) customers can now use Internet Protocol version 6 (IPv6) addresses, via our new dual-stack endpoints to create and manage RAM r...

#AWS #AwsGovcloudUs #AwsResourceAccessManager
AWS Resource Access Manager (RAM) now supports Internet Protocol Version 6 (IPv6)
AWS Resource Access Manager (AWS RAM) customers can now use Internet Protocol version 6 (IPv6) addresses, via our new dual-stack endpoints to create and manage RAM resource shares in your accounts. The existing RAM endpoints supporting IPv4 will remain available for backwards compatibility. The new dual-stack domains are available either from the internet or from within an Amazon Virtual Private Cloud (VPC) using AWS https://aws.amazon.com/privatelink/. To learn more on best practices for configuring IPv6 in your environment, visit the https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/internet-protocol-version-6.html. Support for IPv6 on AWS RAM is available in the https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/, the AWS GovCloud (US) Regions, and the China Regions. To get started with using AWS RAM to share resources, visit the https://console.aws.amazon.com/ram/home.  
aws.amazon.com
March 31, 2025 at 9:05 PM
Sharing of Connections is now available in AWS CodeConnections

AWS CodeConnections now allows you to securely share your https://docs.aws.amazon.com/dtconsole/latest/userguide/connections.html resource across individual AWS accounts or within your AWS Organizati...

#AWS #AwsResourceAccessManager
Sharing of Connections is now available in AWS CodeConnections
AWS CodeConnections now allows you to securely share your https://docs.aws.amazon.com/dtconsole/latest/userguide/connections.html resource across individual AWS accounts or within your AWS Organization. Previously, to create a Connection, you installed the AWS connector App for GitHub or GitLab or Bitbucket for each AWS account from which source access was required. You can now use https://aws.amazon.com/ram/ (RAM) to securely share a Connection to your third-party source provider across AWS accounts. By using AWS RAM to share your Connection resource, you no longer need to create a Connection in each AWS account. Instead, you can create a Connection in an AWS account, and then share the Connection across multiple AWS accounts. By using AWS RAM, you can also automate sharing the connection across AWS accounts, reducing the operational overhead to support a multi-account deployment strategy. To apply fine grained access control, in the AWS account with which a Connection is shared, you can use https://docs.aws.amazon.com/dtconsole/latest/userguide/security_iam_id-based-policy-examples-connections.html to manage what operations an IAM role can perform. To learn more about sharing connections, visit our https://docs.aws.amazon.com/dtconsole/latest/userguide/connections-share.html. To learn more about what Connections in AWS CodeConnections are and how they work, visit our https://docs.aws.amazon.com/dtconsole/latest/userguide/welcome-connections.html.
aws.amazon.com
March 6, 2025 at 7:05 PM
🆕 AWS Resource Access Manager (RAM) now supports IPv6 sharing via dual-stack endpoints. Existing IPv4 endpoints are still available. Available in Commercial, GovCloud, and China regions. See the IPv6 whitepaper for best practices. Start sharing resour…

#AWS #AwsGovcloudUs #AwsResourceAccessManager
AWS Resource Access Manager (RAM) now supports Internet Protocol Version 6 (IPv6)
AWS Resource Access Manager (AWS RAM) customers can now use Internet Protocol version 6 (IPv6) addresses, via our new dual-stack endpoints to create and manage RAM resource shares in your accounts. The existing RAM endpoints supporting IPv4 will remain available for backwards compatibility. The new dual-stack domains are available either from the internet or from within an Amazon Virtual Private Cloud (VPC) using AWS PrivateLink. To learn more on best practices for configuring IPv6 in your environment, visit the whitepaper on IPv6 in AWS. Support for IPv6 on AWS RAM is available in the AWS Commercial Regions, the AWS GovCloud (US) Regions, and the China Regions. To get started with using AWS RAM to share resources, visit the AWS Resource Access Manager Console.
aws.amazon.com
March 31, 2025 at 8:40 PM
🆕 AWS CodeConnections now shares resources across accounts via AWS RAM, removing the need for individual connectors. Use IAM policies for access control. For more, see AWS documentation.

#AWS #AwsResourceAccessManager
Sharing of Connections is now available in AWS CodeConnections
AWS CodeConnections now allows you to securely share your Connection resource across individual AWS accounts or within your AWS Organization. Previously, to create a Connection, you installed the AWS connector App for GitHub or GitLab or Bitbucket for each AWS account from which source access was required. You can now use AWS Resource Access Manager (RAM) to securely share a Connection to your third-party source provider across AWS accounts. By using AWS RAM to share your Connection resource, you no longer need to create a Connection in each AWS account. Instead, you can create a Connection in an AWS account, and then share the Connection across multiple AWS accounts. By using AWS RAM, you can also automate sharing the connection across AWS accounts, reducing the operational overhead to support a multi-account deployment strategy. To apply fine grained access control, in the AWS account with which a Connection is shared, you can use IAM policies to manage what operations an IAM role can perform. To learn more about sharing connections, visit our documentation. To learn more about what Connections in AWS CodeConnections are and how they work, visit our documentation.
aws.amazon.com
March 6, 2025 at 6:40 PM