Schlagwort: cloud computing

AWS Marketplace now supports VAT credit notes for deemed supply refunds

AWS Marketplace sellers can now submit Value Added Tax (VAT) credit notes for refunded deemed supply transactions through a self-service experience in AWS Partner Central. Previously, VAT was disbursed to sellers for eligible transactions, and when a buyer was later refunded, sellers had to contact AWS to submit the corresponding credit note. This launch simplifies post-refund VAT documentation for sellers.
Sellers can view eligible refund line items in the VAT on deemed supply section, select the refunds covered by a credit note, upload a PDF or the applicable electronic invoice format, and track the submission status. Sellers can consolidate multiple eligible refunds into a single credit note where applicable and review the associated financial adjustment in the Seller Insights reporting.
These capabilities are available for eligible AWS Marketplace transactions, including Channel Partner Private Offer (CPPO) transactions, in supported EU member states, Norway, and the United Kingdom. Country-specific invoicing and electronic-invoicing requirements continue to apply.
To get started, sign in to AWS Partner Central and go to Settings → Tax information → VAT on deemed supply. To learn more, visit the AWS Marketplace Seller Guide or Deemed Supply FAQs.
Quelle: aws.amazon.com

AWS Systems Manager simplifies onboarding of Google Cloud VMs for centralized management

AWS Systems Manager Cloud Connector now extends simplified multicloud onboarding support to Google Cloud, making it easy to connect your existing Google Cloud VMs to Systems Manager for centralized management alongside AWS, on-premises, and Azure resources without manual agent installation. Previously, managing virtual machines across multiple cloud providers often required coordinating and setting up configurations separately in each environment.
With Cloud Connector for Google Cloud, you can automatically deploy the SSM Agent to Google Cloud VMs at scale. Once connected, Google Cloud VMs appear alongside EC2 instances, on-premises servers, and other multicloud resources in a unified view, enabling you to use Session Manager, Automation runbooks, Run Command, State Manager, Patch Manager, and Inventory across AWS, on-premises, Azure, and Google Cloud from a single workflow. This simplifies operations for teams managing infrastructure across multiple clouds, enabling them to standardize management practices and reduce operational complexity.
Cloud Connector for Google Cloud is available in Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, New Zealand, Osaka, Seoul, Singapore, Sydney, Taipei, Thailand, Tokyo), Canada (Central, Calgary), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Israel (Tel Aviv), Mexico (Central), South America (Sao Paulo), US East (N. Virginia, Ohio), and US West (N. California, Oregon).
To learn more, visit the AWS Systems Manager documentation.
Quelle: aws.amazon.com

Amazon Bedrock AgentCore Identity now supports OAuth 2.0 discovery URLs

Amazon Bedrock AgentCore Identity now supports OAuth 2.0 authorization server discovery URLs for both inbound JWT authorization and outbound OAuth credential providers. This update enables developers to configure AgentCore with OAuth 2.0 authorization servers that do not use OpenID Connect (OIDC).
Previously, AgentCore Identity accepted only OIDC discovery URLs. Authorization servers that implement OAuth 2.0 without OIDC publish their metadata at a different well-known path and could not be used with AgentCore. With this launch, you can use either OIDC or OAuth 2.0 authorization server discovery URLs when you configure a JWT authorizer or a custom OAuth credential provider on AgentCore.
This feature is available in all AWS Regions where Amazon Bedrock AgentCore is available, at no additional cost. To learn more, see Configure inbound JWT authorizer and Add OAuth client using custom provider in the Amazon Bedrock AgentCore Developer Guide.
Quelle: aws.amazon.com

AWS Batch on Amazon EKS adds Linux capabilities, seccomp, and pod-level settings

AWS Batch now supports additional Kubernetes security context settings in Amazon EKS job definitions, including Linux capabilities, seccomp profiles, and pod-level settings. For EKS clusters that enforce the Kubernetes Pod Security Standards restricted profile, you can now run AWS Batch jobs with only the privileges and system calls they require.
To get started, use the RegisterJobDefinition API to set capabilities and seccompProfile in a container’s securityContext, or set securityContext in podProperties to define pod-wide settings such as fsGroup. Container-level settings override pod-level defaults. You can configure these settings through the AWS Management Console, AWS CLI, AWS SDKs, or AWS CloudFormation.
The additional security context settings for AWS Batch on Amazon EKS are now supported in all AWS Regions where AWS Batch is available. For more information, see the Amazon EKS properties section in the AWS Batch User Guide.
Quelle: aws.amazon.com

AWS Secrets Manager now supports cross-account replication

AWS Secrets Manager now supports cross-account replication, enabling you to maintain a synchronized copy of a primary secret in a secondary AWS account for cross-account access, backup, and disaster recovery. Cross-account replication extends the existing multi-Region replication capability across account boundaries.
With cross-account replication, platform or security teams can own and rotate a secret centrally, and each consuming account gets a local, always-current copy without any shared KMS keys or cross-account secret policies. The replica secret is a full, independent resource, encrypted with a customer managed KMS key owned by the replica account. Secrets Manager updates it automatically whenever the primary secret’s value changes, including rotations.
You can keep a live copy of critical secrets in a dedicated recovery or failover account, isolated from ransomware or a compromised primary account. If needed, the replica can be promoted to a standalone secret.
Cross-account replication is available in all AWS Regions where Secrets Manager is available. For a list of regions where Secrets Manager is available, see the AWS Region table.
To learn more, see Replicate secrets across AWS accounts in the Secrets Manager User Guide and the AssociateCrossAccountReplica API reference. For pricing details, see AWS Secrets Manager pricing.
Quelle: aws.amazon.com

Grok 4.7 now available on Kiro in AWS GovCloud (US)

A new model is now available in the Kiro IDE and CLI for the AWS GovCloud (US) Regions.
Grok 4.7 is SpaceXSI’s most capable model for coding and knowledge work. It’s built to stay focused through hard tasks that run for hours, and it checks its work before moving on. Compared with Grok 4.6, it plans and recovers from errors more reliably in repo-scale coding work. Grok 4.7 is available with experimental support and a 500K context window. Requests up to 200K tokens use a 2.7x credit multiplier, and requests over 200K tokens are billed at 5.4x.
Kiro administrators control which models are available to their users, so organizations can align model access with their internal policies.
Ensure your IDE or CLI is updated to the latest version, then restart it to access the new model from the model selector. For more details, visit the GovCloud documentation, the monitoring and tracking guide, or contact your AWS account team. To learn more about Kiro, visit the Kiro product page.
Quelle: aws.amazon.com

Aurora PostgreSQL with express configuration now supported in CloudFormation

Aurora PostgreSQL now supports express configuration in AWS CloudFormation for infrastructure as code deployment. This launch enables you to automate the infrastructure deployment of your Aurora clusters through CloudFormation templates while benefiting from the speed of express configuration.
Aurora PostgreSQL clusters created with express configuration allow you to create and query an Aurora serverless database in seconds. The new withExpressConfiguration createOnly property on the AWS::RDS::DBCluster resource creates both the cluster and its primary database instance from one property declaration. You don’t need to model or manage the instance separately in your CloudFormation template. This simplifies your templates and makes it easier to manage Aurora clusters with express configuration through infrastructure as code.
The CloudFormation support is available in all AWS Regions where Aurora PostgreSQL with express configuration is offered. To learn more, see the Aurora User Guide and the AWS::RDS::DBCluster resource reference in the AWS CloudFormation documentation.
Quelle: aws.amazon.com