Is Code-Artifact scheduled 443-port-removal change delayed ?

0

We were expecting this change Code-Artifact-Operational-Change to take effect as of March 27, 2023. However, it seems like it's not there yet. Any idea why it didn't happen on the scheduled date?

If i understood correctly, The summary of this change was that, CodeArtifact will no longer return the 443 port on the generated urls in the package-lock/yarn.lock files. However, in my case it seems like CodeArtifact is still returning the urls with 443 port appended.

  • Tried cleaning my npm/yarn cache.
  • Tried deleting the entire lock file and re-generated it again.

Is there something we have to do on our end for this change to take effect?

질문됨 일 년 전268회 조회
1개 답변
1
수락된 답변

Hi,

This change has not yet been enabled in all regions. It is currently enabled in:

  • ap-south-1
  • ap-southeast-1
  • ap-southeast-2
  • ap-northeast-1
  • eu-west-3
  • eu-south-1
  • eu-central-1

Additional regions will be enabled this week. You do not need to take any action for this to occur.

profile pictureAWS
답변함 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠